Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b7fd1a6f449db1c702ba0a5749ee1503749e0cc6ff66a93fe16f56feab346e5

Tx prefix hash: 55f27c8dc5b10cabda1c4c6c05939b4a32a353d86b7490ced739b7809c319967
Tx public key: 53a1d18d2f0eead73e06c7028137b264607b400a625e5a6a0fb64da7deaf9a89
Timestamp: 1722461617 Timestamp [UCT]: 2024-07-31 21:33:37 Age [y:d:h:m:s]: 00:248:11:09:18
Block: 1077959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177482 RingCT/type: yes/0
Extra: 0153a1d18d2f0eead73e06c7028137b264607b400a625e5a6a0fb64da7deaf9a89021100000012e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 461c604c1069a03544150b189b4e90ccb3af8a380882ba2393cc6bf54f9bd111 0.600000000000 1550514 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": 1077969, "vin": [ { "gen": { "height": 1077959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "461c604c1069a03544150b189b4e90ccb3af8a380882ba2393cc6bf54f9bd111" } } ], "extra": [ 1, 83, 161, 209, 141, 47, 14, 234, 215, 62, 6, 199, 2, 129, 55, 178, 100, 96, 123, 64, 10, 98, 94, 90, 106, 15, 182, 77, 167, 222, 175, 154, 137, 2, 17, 0, 0, 0, 18, 233, 20, 221, 21, 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