Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37853effa927d23cb61c09b63330fb99372e6f79e3705b617b273ed71deb2999

Tx prefix hash: 9fa2d287ea4cb5dc65c5a04db8aa5ac4ca5f3ab39dade0978dfe8568a54b755c
Tx public key: d86031ca5c9ac624cae00bfba46fc5d1b094fd2992e66695825b9159b3723823
Timestamp: 1737438733 Timestamp [UCT]: 2025-01-21 05:52:13 Age [y:d:h:m:s]: 00:148:06:44:34
Block: 1201939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105720 RingCT/type: yes/0
Extra: 01d86031ca5c9ac624cae00bfba46fc5d1b094fd2992e66695825b9159b3723823021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d31a6f169a192b2a1dbcfc4605b503ffc226dcf3c6592c10da800fc8e111e5d 0.600000000000 1688598 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": 1201949, "vin": [ { "gen": { "height": 1201939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d31a6f169a192b2a1dbcfc4605b503ffc226dcf3c6592c10da800fc8e111e5d" } } ], "extra": [ 1, 216, 96, 49, 202, 92, 154, 198, 36, 202, 224, 11, 251, 164, 111, 197, 209, 176, 148, 253, 41, 146, 230, 102, 149, 130, 91, 145, 89, 179, 114, 56, 35, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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