Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68b6ebd301493642c5fc585382d1b43393e0e5f2630348bed2aa3ee5f4f5695e

Tx prefix hash: d20c42152cce76189c628e00023b81eba459680852100a4ae0fa11e41d342400
Tx public key: be1535e7e68e0c5f39635cbc03d0a0949d05c9387b0f0611a14a0d338bf620b9
Timestamp: 1703171229 Timestamp [UCT]: 2023-12-21 15:07:09 Age [y:d:h:m:s]: 01:086:08:29:50
Block: 918033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322850 RingCT/type: yes/0
Extra: 01be1535e7e68e0c5f39635cbc03d0a0949d05c9387b0f0611a14a0d338bf620b90211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f65037a4ae57022b45d9ad8f8cedcb939a7697d04b2fcbfc4fa0dff9142030fa 0.600000000000 1375669 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": 918043, "vin": [ { "gen": { "height": 918033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f65037a4ae57022b45d9ad8f8cedcb939a7697d04b2fcbfc4fa0dff9142030fa" } } ], "extra": [ 1, 190, 21, 53, 231, 230, 142, 12, 95, 57, 99, 92, 188, 3, 208, 160, 148, 157, 5, 201, 56, 123, 15, 6, 17, 161, 74, 13, 51, 139, 246, 32, 185, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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