Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfa278411293007270397ccc6b358b22303e8528cd6978229501b8b67828bdfb

Tx prefix hash: ac5e0b081a48df83d5192872d52f68e4702c814196cf2ae05dab9597bde75949
Tx public key: 9499da2ae8f69ae36638f8164ebaccc2e25e80e24a3e882d37a11397838cd223
Timestamp: 1650789101 Timestamp [UCT]: 2022-04-24 08:31:41 Age [y:d:h:m:s]: 02:244:14:32:07
Block: 486979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 694789 RingCT/type: yes/0
Extra: 019499da2ae8f69ae36638f8164ebaccc2e25e80e24a3e882d37a11397838cd223021100000002faf35c9c000000000000000000

1 output(s) for total of 14.942960312000 dcy

stealth address amount amount idx
00: a6b7a2f3c427e18de46ea6ee0e8751da02002fbdeff3b68efecc4e88f3f227a3 14.942960312000 909364 of 0

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": 486989, "vin": [ { "gen": { "height": 486979 } } ], "vout": [ { "amount": 14942960312, "target": { "key": "a6b7a2f3c427e18de46ea6ee0e8751da02002fbdeff3b68efecc4e88f3f227a3" } } ], "extra": [ 1, 148, 153, 218, 42, 232, 246, 154, 227, 102, 56, 248, 22, 78, 186, 204, 194, 226, 94, 128, 226, 74, 62, 136, 45, 55, 161, 19, 151, 131, 140, 210, 35, 2, 17, 0, 0, 0, 2, 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