Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46ff34a0c69019bcf8a1492c07bf6d2c9fa08e89eaef2c5368ab31b39d47e13d

Tx prefix hash: a08518fe299d6c32c838a94003b10bcfc042866944ac711f5193be3e6086de4a
Tx public key: 8ca01ea7aa84c71fcd39c7dd83a08f1fd086b50e5d451b67d5a838552c2f0c0f
Timestamp: 1701622447 Timestamp [UCT]: 2023-12-03 16:54:07 Age [y:d:h:m:s]: 01:048:09:54:11
Block: 905199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295929 RingCT/type: yes/0
Extra: 018ca01ea7aa84c71fcd39c7dd83a08f1fd086b50e5d451b67d5a838552c2f0c0f02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.614751961000 dcy

stealth address amount amount idx
00: df2613819b5411d6eb21e44693e8be31cb99fccbec2505be463a83df0328db82 0.614751961000 1362074 of 0

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": 905209, "vin": [ { "gen": { "height": 905199 } } ], "vout": [ { "amount": 614751961, "target": { "key": "df2613819b5411d6eb21e44693e8be31cb99fccbec2505be463a83df0328db82" } } ], "extra": [ 1, 140, 160, 30, 167, 170, 132, 199, 31, 205, 57, 199, 221, 131, 160, 143, 31, 208, 134, 181, 14, 93, 69, 27, 103, 213, 168, 56, 85, 44, 47, 12, 15, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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