Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96ecf03b1181f7e6518ce4aef389a3bf76127caddd3fda8ac880d28f8585d076

Tx prefix hash: bbc20c1dd6a23beab1fd8ed989cc8a86bc4656bea63aa88cb17ae1d346ed5f56
Tx public key: 8aab7546250e6cf6f3d23d71785509eb1edcb2dca94b2aa3e3fb2cf297ddb706
Timestamp: 1734464166 Timestamp [UCT]: 2024-12-17 19:36:06 Age [y:d:h:m:s]: 00:112:22:57:30
Block: 1177379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80499 RingCT/type: yes/0
Extra: 018aab7546250e6cf6f3d23d71785509eb1edcb2dca94b2aa3e3fb2cf297ddb7060211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad71bad0ed53a5063bbd54a1199059266d82b45f3fe96d239714f849637806d5 0.600000000000 1663750 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": 1177389, "vin": [ { "gen": { "height": 1177379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad71bad0ed53a5063bbd54a1199059266d82b45f3fe96d239714f849637806d5" } } ], "extra": [ 1, 138, 171, 117, 70, 37, 14, 108, 246, 243, 210, 61, 113, 120, 85, 9, 235, 30, 220, 178, 220, 169, 75, 42, 163, 227, 251, 44, 242, 151, 221, 183, 6, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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