Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89e92e916f7f2f2a9b1b165f65732e36d1af4d9f3c8b7506f7918ff2f06e97ad

Tx prefix hash: 618a46488855942d153ab31539590b404d5c6287122beae340ac647311736589
Tx public key: b3daeacb958e97f827c74cf81935a6bd8dc7385b9514610b957d6c20775c3f04
Timestamp: 1736094940 Timestamp [UCT]: 2025-01-05 16:35:40 Age [y:d:h:m:s]: 00:162:11:32:31
Block: 1190870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115832 RingCT/type: yes/0
Extra: 01b3daeacb958e97f827c74cf81935a6bd8dc7385b9514610b957d6c20775c3f0402110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f7f0513660df9a60077fa700e6bb96b325d85a4ddf3b13d8276864cbd98eacb 0.600000000000 1677391 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": 1190880, "vin": [ { "gen": { "height": 1190870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f7f0513660df9a60077fa700e6bb96b325d85a4ddf3b13d8276864cbd98eacb" } } ], "extra": [ 1, 179, 218, 234, 203, 149, 142, 151, 248, 39, 199, 76, 248, 25, 53, 166, 189, 141, 199, 56, 91, 149, 20, 97, 11, 149, 125, 108, 32, 119, 92, 63, 4, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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