Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66b95575a7c7850fc637b28ca2cc28faf04109a389a9ec352824db473f620973

Tx prefix hash: 0a5c6d9b76174851d6d8bea5b143dbb144353bc6021e3715e7a6ac730d9e5c1d
Tx public key: 7099a772bddc817b629a0fca547ec8ba05eaa85fb7876f16ff05ee4036f718e8
Timestamp: 1715469798 Timestamp [UCT]: 2024-05-11 23:23:18 Age [y:d:h:m:s]: 00:186:10:29:53
Block: 1020027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133420 RingCT/type: yes/0
Extra: 017099a772bddc817b629a0fca547ec8ba05eaa85fb7876f16ff05ee4036f718e802110000001159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 633ccac85e32f01a60c429ffe1d215a3a21acdbc888a2c0cda838e2afe8730ca 0.600000000000 1484086 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": 1020037, "vin": [ { "gen": { "height": 1020027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "633ccac85e32f01a60c429ffe1d215a3a21acdbc888a2c0cda838e2afe8730ca" } } ], "extra": [ 1, 112, 153, 167, 114, 189, 220, 129, 123, 98, 154, 15, 202, 84, 126, 200, 186, 5, 234, 168, 95, 183, 135, 111, 22, 255, 5, 238, 64, 54, 247, 24, 232, 2, 17, 0, 0, 0, 17, 89, 218, 211, 245, 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