Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ee47d5c5d0e1e612c53eee2422cd3f06dfc2f58879733eac3bf97625b734e23

Tx prefix hash: f93008eeed53a07f0c6709136615c22c84b22ffa035c35ad7b709d357000d42d
Tx public key: 06aa70635d355fe7e9ea6d0d7dbcc3f8f124e92cb2ba994ae47b9e4f7923facc
Timestamp: 1713560098 Timestamp [UCT]: 2024-04-19 20:54:58 Age [y:d:h:m:s]: 00:154:11:51:20
Block: 1004145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110684 RingCT/type: yes/0
Extra: 0106aa70635d355fe7e9ea6d0d7dbcc3f8f124e92cb2ba994ae47b9e4f7923facc0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41d20ce1e90864b78e71ec62657ac0be430aa20fa334518c05a2e5bcaefadd0f 0.600000000000 1464713 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": 1004155, "vin": [ { "gen": { "height": 1004145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41d20ce1e90864b78e71ec62657ac0be430aa20fa334518c05a2e5bcaefadd0f" } } ], "extra": [ 1, 6, 170, 112, 99, 93, 53, 95, 231, 233, 234, 109, 13, 125, 188, 195, 248, 241, 36, 233, 44, 178, 186, 153, 74, 228, 123, 158, 79, 121, 35, 250, 204, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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