Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a677f60d8d7c6ebce666329352bc3d35b2dd769a300a25dca339f4a0f583a7e

Tx prefix hash: 74adccbcd1684a64988a5c0332fac4435d4bc4d1bd10fc7542b8eb03e5958c3e
Tx public key: 0ecac8f261a5b26beaf36aa592e7ed10dfcc4c77d797c42f33cf3214d96d0ed7
Timestamp: 1721200313 Timestamp [UCT]: 2024-07-17 07:11:53 Age [y:d:h:m:s]: 00:287:15:01:55
Block: 1067524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205481 RingCT/type: yes/0
Extra: 010ecac8f261a5b26beaf36aa592e7ed10dfcc4c77d797c42f33cf3214d96d0ed7021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: add1664f47e2ba61120a7a3498124a23733a912b0d11bb83490309760f10b852 0.600000000000 1538353 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": 1067534, "vin": [ { "gen": { "height": 1067524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "add1664f47e2ba61120a7a3498124a23733a912b0d11bb83490309760f10b852" } } ], "extra": [ 1, 14, 202, 200, 242, 97, 165, 178, 107, 234, 243, 106, 165, 146, 231, 237, 16, 223, 204, 76, 119, 215, 151, 196, 47, 51, 207, 50, 20, 217, 109, 14, 215, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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