Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2f39e1a723eea40cdfa679f96dce4e906003f0d89e9e2b8b18da181949f4c64

Tx prefix hash: 564a45ec8b0cadd20c40d46140e65672294c4e4e26547fdd1c10dec6476b00ca
Tx public key: 83f3f4eaff3d82383503c86c4385483dd6b00d0d68e3de7c4a7dc782e3de7a13
Timestamp: 1617200124 Timestamp [UCT]: 2021-03-31 14:15:24 Age [y:d:h:m:s]: 04:192:11:36:41
Block: 230463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155381 RingCT/type: yes/0
Extra: 0183f3f4eaff3d82383503c86c4385483dd6b00d0d68e3de7c4a7dc782e3de7a1302110000000c3634f08d000000000000000000

1 output(s) for total of 105.774502703000 dcy

stealth address amount amount idx
00: 5ac92bdfd64d32ba490ecd7ea964abc31944239841dad2e1ecd511d1e7d08b96 105.774502703000 478397 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": 230473, "vin": [ { "gen": { "height": 230463 } } ], "vout": [ { "amount": 105774502703, "target": { "key": "5ac92bdfd64d32ba490ecd7ea964abc31944239841dad2e1ecd511d1e7d08b96" } } ], "extra": [ 1, 131, 243, 244, 234, 255, 61, 130, 56, 53, 3, 200, 108, 67, 133, 72, 61, 214, 176, 13, 13, 104, 227, 222, 124, 74, 125, 199, 130, 227, 222, 122, 19, 2, 17, 0, 0, 0, 12, 54, 52, 240, 141, 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