Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcc1db7fff1606ab9b4f286ea3c399f44d26992e78e1157830739e41e7eba783

Tx prefix hash: 4ced612ac1032464c7d778a44321cb06c44f4441b58274c54c08256a1de1a4e3
Tx public key: 61df08a4f16f8c64c40f0981e9b6cdcc99179dd551565c1db727dba8406fbed6
Timestamp: 1577991018 Timestamp [UCT]: 2020-01-02 18:50:18 Age [y:d:h:m:s]: 05:065:02:21:57
Block: 37380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196260 RingCT/type: yes/0
Extra: 0161df08a4f16f8c64c40f0981e9b6cdcc99179dd551565c1db727dba8406fbed60211000000134943cd9f000000000000000000

1 output(s) for total of 461.472041576000 dcy

stealth address amount amount idx
00: cd857b7233221bc64edfc030e4aebf59b43a06b0aae4adc771d20c2f58f4283b 461.472041576000 63428 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": 37390, "vin": [ { "gen": { "height": 37380 } } ], "vout": [ { "amount": 461472041576, "target": { "key": "cd857b7233221bc64edfc030e4aebf59b43a06b0aae4adc771d20c2f58f4283b" } } ], "extra": [ 1, 97, 223, 8, 164, 241, 111, 140, 100, 196, 15, 9, 129, 233, 182, 205, 204, 153, 23, 157, 213, 81, 86, 92, 29, 183, 39, 219, 168, 64, 111, 190, 214, 2, 17, 0, 0, 0, 19, 73, 67, 205, 159, 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