Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b642edc8bde3a01594ef2a8b6a214d1590504372120687b83933e0cfc87de5a3

Tx prefix hash: aea29488662258991045e28846d73e06a82aece3a9e811ed0fedfb333960c7e8
Tx public key: eb8cd0dd7ecfb9d5f3163033f83d572d37d6719277c11712b2afb05254aaf36f
Timestamp: 1736253257 Timestamp [UCT]: 2025-01-07 12:34:17 Age [y:d:h:m:s]: 00:093:00:05:59
Block: 1192165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66257 RingCT/type: yes/0
Extra: 01eb8cd0dd7ecfb9d5f3163033f83d572d37d6719277c11712b2afb05254aaf36f0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c737d2940432109413076afe8b2fdd2f8dfbebc70aede8faaa98492f973a968 0.600000000000 1678714 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": 1192175, "vin": [ { "gen": { "height": 1192165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c737d2940432109413076afe8b2fdd2f8dfbebc70aede8faaa98492f973a968" } } ], "extra": [ 1, 235, 140, 208, 221, 126, 207, 185, 213, 243, 22, 48, 51, 248, 61, 87, 45, 55, 214, 113, 146, 119, 193, 23, 18, 178, 175, 176, 82, 84, 170, 243, 111, 2, 17, 0, 0, 0, 3, 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