Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff2a506f3877344de62a136e2eedf7bb3be6792bc2521153dbee73cfdbc35414

Tx prefix hash: 600bf36e765b8467785b3d6aa0b0ec4fc7757143e53dea317ca1c40031060de3
Tx public key: 564fd9df94d6aecd06e9b7a96043a62ade286414ae941435d677b28c00cdd861
Timestamp: 1734390627 Timestamp [UCT]: 2024-12-16 23:10:27 Age [y:d:h:m:s]: 00:091:04:06:30
Block: 1176766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64934 RingCT/type: yes/0
Extra: 01564fd9df94d6aecd06e9b7a96043a62ade286414ae941435d677b28c00cdd861021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81a2fb739dcee2f064c08367a4503d9e3e253e009b7c264fdef4d17cb9a1ffed 0.600000000000 1663127 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": 1176776, "vin": [ { "gen": { "height": 1176766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81a2fb739dcee2f064c08367a4503d9e3e253e009b7c264fdef4d17cb9a1ffed" } } ], "extra": [ 1, 86, 79, 217, 223, 148, 214, 174, 205, 6, 233, 183, 169, 96, 67, 166, 42, 222, 40, 100, 20, 174, 148, 20, 53, 214, 119, 178, 140, 0, 205, 216, 97, 2, 17, 0, 0, 0, 2, 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