Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ff183da24fb6ea2e0a12744d8329c9222d8439ee78d6e07493d858e504e8a93

Tx prefix hash: 494fec7c733161a641d0e2cf25f39aeba394013c4b8be82f5486a3923aef6765
Tx public key: a1d07c1cf3180cdd133a8d82a724dcc692ae8a09b31de4028a5e85f4242fac77
Timestamp: 1735994895 Timestamp [UCT]: 2025-01-04 12:48:15 Age [y:d:h:m:s]: 00:164:08:50:50
Block: 1190035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117173 RingCT/type: yes/0
Extra: 01a1d07c1cf3180cdd133a8d82a724dcc692ae8a09b31de4028a5e85f4242fac770211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ac14afc4624e62e017ed3470f029697130f53b10967a1a016d3feb56ad35aa6 0.600000000000 1676550 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": 1190045, "vin": [ { "gen": { "height": 1190035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ac14afc4624e62e017ed3470f029697130f53b10967a1a016d3feb56ad35aa6" } } ], "extra": [ 1, 161, 208, 124, 28, 243, 24, 12, 221, 19, 58, 141, 130, 167, 36, 220, 198, 146, 174, 138, 9, 179, 29, 228, 2, 138, 94, 133, 244, 36, 47, 172, 119, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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