Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6e360b3e128de5a69e0396b6e95aa8c027673af4f4be471499361a088d3faf3

Tx prefix hash: 0a2d97a024c4696ed37638cc97b3aa566ebfbf2eb79077f0a0439afb53953d80
Tx public key: d5bc22ad122d0616affaef9c43aeb68542d2c2a3861d50b1e6df7710e2f9142c
Timestamp: 1580692872 Timestamp [UCT]: 2020-02-03 01:21:12 Age [y:d:h:m:s]: 05:113:01:08:08
Block: 57407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1232910 RingCT/type: yes/0
Extra: 01d5bc22ad122d0616affaef9c43aeb68542d2c2a3861d50b1e6df7710e2f9142c0211000000d217786bcf000000000000000000

1 output(s) for total of 396.084274629000 dcy

stealth address amount amount idx
00: 7bdea9d2e8847e5f711fc8c8a3860d21012cb25882a18670cff70b0438dd1f39 396.084274629000 106111 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": 57417, "vin": [ { "gen": { "height": 57407 } } ], "vout": [ { "amount": 396084274629, "target": { "key": "7bdea9d2e8847e5f711fc8c8a3860d21012cb25882a18670cff70b0438dd1f39" } } ], "extra": [ 1, 213, 188, 34, 173, 18, 45, 6, 22, 175, 250, 239, 156, 67, 174, 182, 133, 66, 210, 194, 163, 134, 29, 80, 177, 230, 223, 119, 16, 226, 249, 20, 44, 2, 17, 0, 0, 0, 210, 23, 120, 107, 207, 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