Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fdebca817011842b2f4ab06572c3523a65c44cb9e074e1e01eda7a200b6b314

Tx prefix hash: 6146850754f16ef8a0be41c82bc17407e257e393fe9a2ca549a61712a978d3a0
Tx public key: bf004291f0ab9379ce5ef65de01e5c75905ed449b1df423b5309f5001c5cc2b5
Timestamp: 1702423542 Timestamp [UCT]: 2023-12-12 23:25:42 Age [y:d:h:m:s]: 01:114:19:38:50
Block: 911857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343172 RingCT/type: yes/0
Extra: 01bf004291f0ab9379ce5ef65de01e5c75905ed449b1df423b5309f5001c5cc2b5021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e5e90291093f4f13a00ec7fa890662d0349bdee5879dd482587fddeb931c948 0.600000000000 1369073 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": 911867, "vin": [ { "gen": { "height": 911857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e5e90291093f4f13a00ec7fa890662d0349bdee5879dd482587fddeb931c948" } } ], "extra": [ 1, 191, 0, 66, 145, 240, 171, 147, 121, 206, 94, 246, 93, 224, 30, 92, 117, 144, 94, 212, 73, 177, 223, 66, 59, 83, 9, 245, 0, 28, 92, 194, 181, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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