Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1f436e4391ceb9d46d546d7edfa3e7685e1db67d331791d3ffb2c0aede669ae

Tx prefix hash: b04842da82c66a6ea87673748fc0786f9735c3bbb5822cea698d6a0e88181595
Tx public key: 42eefb0bbc0fd0cc64fd76033f26fa93d5f6f45ad737912ca47bb74938acf26f
Timestamp: 1702868441 Timestamp [UCT]: 2023-12-18 03:00:41 Age [y:d:h:m:s]: 01:045:05:17:25
Block: 915523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293413 RingCT/type: yes/0
Extra: 0142eefb0bbc0fd0cc64fd76033f26fa93d5f6f45ad737912ca47bb74938acf26f021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fbc6c66ca821c0c6c1addd838df9d9bd0b363e5db77ccbee62a2a7166441dfe 0.600000000000 1372919 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": 915533, "vin": [ { "gen": { "height": 915523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fbc6c66ca821c0c6c1addd838df9d9bd0b363e5db77ccbee62a2a7166441dfe" } } ], "extra": [ 1, 66, 238, 251, 11, 188, 15, 208, 204, 100, 253, 118, 3, 63, 38, 250, 147, 213, 246, 244, 90, 215, 55, 145, 44, 164, 123, 183, 73, 56, 172, 242, 111, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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