Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: e7866625d30d3037a3d170264212c55f562e38fc669b2980826ada1e35725613

Tx prefix hash: 6dadce65ad0e57068d2b74e175eb0ed7dd615dec4b0adee1e44ce8661ed60dfa
Tx public key: 9b33f50a01e942916711dd0f8b741bcd0dc4c158cb01027d8058a38358b3b5b2
Timestamp: 1719156064 Timestamp [UCT]: 2024-06-23 15:21:04 Age [y:d:h:m:s]: 01:137:23:02:26
Block: 1050538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357166 RingCT/type: yes/0
Extra: 019b33f50a01e942916711dd0f8b741bcd0dc4c158cb01027d8058a38358b3b5b202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5f5c7385ed727f1e09021ee5f9fb17fde03bfedbbb7a4a7e8a7207e457bc009 0.600000000000 1520713 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1050548, "vin": [ { "gen": { "height": 1050538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5f5c7385ed727f1e09021ee5f9fb17fde03bfedbbb7a4a7e8a7207e457bc009" } } ], "extra": [ 1, 155, 51, 245, 10, 1, 233, 66, 145, 103, 17, 221, 15, 139, 116, 27, 205, 13, 196, 193, 88, 203, 1, 2, 125, 128, 88, 163, 131, 88, 179, 181, 178, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8