Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69d0f2f863a4aa1fe12233bb1ba796a0b70f775ec2b22f077f8ee0bbb54cf917

Tx prefix hash: d4b13a2e7acb708a8a00f77118e9b34cb0e3b48596be47254c41bd4926f79a54
Tx public key: 7d87f0586f967846d9629483f769f6dc1b2f1f612d82518e47a73bd4fa15f877
Timestamp: 1698574424 Timestamp [UCT]: 2023-10-29 10:13:44 Age [y:d:h:m:s]: 01:194:06:33:37
Block: 880144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399853 RingCT/type: yes/0
Extra: 017d87f0586f967846d9629483f769f6dc1b2f1f612d82518e47a73bd4fa15f877021100000002faf35c9c000000000000000000

1 output(s) for total of 0.744247827000 dcy

stealth address amount amount idx
00: d22134b418795ae856eeb346539106a1f1905f857d785219bb79d99fb61d5fe0 0.744247827000 1335690 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": 880154, "vin": [ { "gen": { "height": 880144 } } ], "vout": [ { "amount": 744247827, "target": { "key": "d22134b418795ae856eeb346539106a1f1905f857d785219bb79d99fb61d5fe0" } } ], "extra": [ 1, 125, 135, 240, 88, 111, 150, 120, 70, 217, 98, 148, 131, 247, 105, 246, 220, 27, 47, 31, 97, 45, 130, 81, 142, 71, 167, 59, 212, 250, 21, 248, 119, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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