Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 437cf60de9e35d7b2aeb322fb78a8bf5f46c231f2bad4fc93bc0b8536c8a666f

Tx prefix hash: dd3f56251432b23f9b4103797debbde9605d64f1c3d7edd2f121b18a3e1e3b5d
Tx public key: 791872b1ab1f2d0f6e67a2780aff836be9ea12c2baa78451501f859c1ba47444
Timestamp: 1711803554 Timestamp [UCT]: 2024-03-30 12:59:14 Age [y:d:h:m:s]: 01:192:05:43:51
Block: 989626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396006 RingCT/type: yes/0
Extra: 01791872b1ab1f2d0f6e67a2780aff836be9ea12c2baa78451501f859c1ba474440211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73459c710c5b7ea9775b6ec0dcb6aa777a8217e4989a8141c479b1cb34aecd5a 0.600000000000 1449929 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": 989636, "vin": [ { "gen": { "height": 989626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73459c710c5b7ea9775b6ec0dcb6aa777a8217e4989a8141c479b1cb34aecd5a" } } ], "extra": [ 1, 121, 24, 114, 177, 171, 31, 45, 15, 110, 103, 162, 120, 10, 255, 131, 107, 233, 234, 18, 194, 186, 167, 132, 81, 80, 31, 133, 156, 27, 164, 116, 68, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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