Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 699f92e0af1296d2f3816a155d88f3439acff4933f23d811376150747f784c15

Tx prefix hash: 41ea64772ed3aef842e1e78f5d6fd9aac0092402128c39af47c057ce1f3a5e65
Tx public key: 832e02154e712266f7c6422b087e7634b956f80b0e024ecd455f15a73400851d
Timestamp: 1732640533 Timestamp [UCT]: 2024-11-26 17:02:13 Age [y:d:h:m:s]: 00:126:13:17:47
Block: 1162256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90242 RingCT/type: yes/0
Extra: 01832e02154e712266f7c6422b087e7634b956f80b0e024ecd455f15a73400851d021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e888fb62d10bf36a1dc80596a6caf9220e9498dc6e64532bf2ae51bfe60ce6da 0.600000000000 1647911 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": 1162266, "vin": [ { "gen": { "height": 1162256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e888fb62d10bf36a1dc80596a6caf9220e9498dc6e64532bf2ae51bfe60ce6da" } } ], "extra": [ 1, 131, 46, 2, 21, 78, 113, 34, 102, 247, 198, 66, 43, 8, 126, 118, 52, 185, 86, 248, 11, 14, 2, 78, 205, 69, 95, 21, 167, 52, 0, 133, 29, 2, 17, 0, 0, 0, 6, 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