Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eae31850ba4ebbfe96c7b49097654da293832587f3a1436cba7649a7d289303c

Tx prefix hash: 56e3f271f8ff853eba31a027c89c1fd4d0d1cc4d24e7495b73e6a3ee6dc403ca
Tx public key: 86513fc8300ab0acf246252b8637d1dfa1fe64ed1469922eab0294aa4141a063
Timestamp: 1711064229 Timestamp [UCT]: 2024-03-21 23:37:09 Age [y:d:h:m:s]: 01:036:21:18:39
Block: 983495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287341 RingCT/type: yes/0
Extra: 0186513fc8300ab0acf246252b8637d1dfa1fe64ed1469922eab0294aa4141a063021100000002a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98d506f454fde7ed33e432b48fc4b3cb0886edb50939740ee413c46d8aaa5e70 0.600000000000 1443634 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": 983505, "vin": [ { "gen": { "height": 983495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98d506f454fde7ed33e432b48fc4b3cb0886edb50939740ee413c46d8aaa5e70" } } ], "extra": [ 1, 134, 81, 63, 200, 48, 10, 176, 172, 242, 70, 37, 43, 134, 55, 209, 223, 161, 254, 100, 237, 20, 105, 146, 46, 171, 2, 148, 170, 65, 65, 160, 99, 2, 17, 0, 0, 0, 2, 165, 223, 157, 134, 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