Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8140adabfe9ef6e94fe9bc8fa52d8d51f72e832cb6a169a5d4acca540436d99a

Tx prefix hash: a72635c4d920916b66d8df15e50cd5f3a37173a98c24ed9da620b5848e715054
Tx public key: 3ad2280c275eeefdd001b6670e016829b6104a7b552ea4a1253387c8550a8767
Timestamp: 1736383095 Timestamp [UCT]: 2025-01-09 00:38:15 Age [y:d:h:m:s]: 00:122:07:44:19
Block: 1193241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87234 RingCT/type: yes/0
Extra: 013ad2280c275eeefdd001b6670e016829b6104a7b552ea4a1253387c8550a8767021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b5d4e5202d7a0fdd7f5b37ddad26a963ea68cb86256771039c489c12a8445c4 0.600000000000 1679800 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": 1193251, "vin": [ { "gen": { "height": 1193241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b5d4e5202d7a0fdd7f5b37ddad26a963ea68cb86256771039c489c12a8445c4" } } ], "extra": [ 1, 58, 210, 40, 12, 39, 94, 238, 253, 208, 1, 182, 103, 14, 1, 104, 41, 182, 16, 74, 123, 85, 46, 164, 161, 37, 51, 135, 200, 85, 10, 135, 103, 2, 17, 0, 0, 0, 5, 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