Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a43eb191d69bb397f6aacfb5b8951c0838b634af036d76f58322c546fae39df

Tx prefix hash: 36219e2228fc30b73508a0021d0a5bdd8753477020b4fbf620dcd9de4cb1a5cf
Tx public key: fca9e910f4f147032b20f335cc4ab2f8c5147f58d3f56578d992e026037752c6
Timestamp: 1718019449 Timestamp [UCT]: 2024-06-10 11:37:29 Age [y:d:h:m:s]: 00:167:06:04:04
Block: 1041142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119698 RingCT/type: yes/0
Extra: 01fca9e910f4f147032b20f335cc4ab2f8c5147f58d3f56578d992e026037752c60211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 725821496b5a332a50f51ae5bb4220a2b1eec632e19eb64e6f88f03b52114183 0.600000000000 1509807 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": 1041152, "vin": [ { "gen": { "height": 1041142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "725821496b5a332a50f51ae5bb4220a2b1eec632e19eb64e6f88f03b52114183" } } ], "extra": [ 1, 252, 169, 233, 16, 244, 241, 71, 3, 43, 32, 243, 53, 204, 74, 178, 248, 197, 20, 127, 88, 211, 245, 101, 120, 217, 146, 224, 38, 3, 119, 82, 198, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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