Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8aea5d7e419c9a1c7c51ba4dad7bf04bcdfd6ecb04a02381021949e80d3cb8c6

Tx prefix hash: 21c7bd564888bf749aa8b6f4f6a75e05a025a1c0e9176070a003764cd4e9a7ce
Tx public key: 248c131a811dd686033c82716bb48220564e49daf136af4b66f23e3da241acde
Timestamp: 1735685258 Timestamp [UCT]: 2024-12-31 22:47:38 Age [y:d:h:m:s]: 00:357:00:10:48
Block: 1187460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252705 RingCT/type: yes/0
Extra: 01248c131a811dd686033c82716bb48220564e49daf136af4b66f23e3da241acde021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bef5e80ee24c86741f6f96a75ec3b85dfe662a02ebd4db49cb3cfedcb723e2a7 0.600000000000 1673951 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": 1187470, "vin": [ { "gen": { "height": 1187460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bef5e80ee24c86741f6f96a75ec3b85dfe662a02ebd4db49cb3cfedcb723e2a7" } } ], "extra": [ 1, 36, 140, 19, 26, 129, 29, 214, 134, 3, 60, 130, 113, 107, 180, 130, 32, 86, 78, 73, 218, 241, 54, 175, 75, 102, 242, 62, 61, 162, 65, 172, 222, 2, 17, 0, 0, 0, 1, 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