Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ddd39bb1daffbf2bdd9eb28820c39199fba4dde21fb198073a157aef1952a73

Tx prefix hash: 131051cbe0c074e0f002c7abf13863f212fcdf7d15989d15a4b1370293babd09
Tx public key: e524df8fb670222d5944cf618df4c03bcf50ec9ec9a79bfa053cdb02e3ddf105
Timestamp: 1623814394 Timestamp [UCT]: 2021-06-16 03:33:14 Age [y:d:h:m:s]: 03:208:05:04:02
Block: 278685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 914792 RingCT/type: yes/0
Extra: 01e524df8fb670222d5944cf618df4c03bcf50ec9ec9a79bfa053cdb02e3ddf105021100000001ece3035d000000000000000000

1 output(s) for total of 73.220939603000 dcy

stealth address amount amount idx
00: 0d8c36f5b5ed9599cb2165bb0b558f58021adf7f80a513b5331a7e7d604069a9 73.220939603000 583874 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": 278695, "vin": [ { "gen": { "height": 278685 } } ], "vout": [ { "amount": 73220939603, "target": { "key": "0d8c36f5b5ed9599cb2165bb0b558f58021adf7f80a513b5331a7e7d604069a9" } } ], "extra": [ 1, 229, 36, 223, 143, 182, 112, 34, 45, 89, 68, 207, 97, 141, 244, 192, 59, 207, 80, 236, 158, 201, 167, 155, 250, 5, 60, 219, 2, 227, 221, 241, 5, 2, 17, 0, 0, 0, 1, 236, 227, 3, 93, 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