Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5fc7e8a8c4f503a9223cb8f907c8cb783add8990f6442772dcd258b7da26aff

Tx prefix hash: a46f9deabdfd652ed69a8fe61682018201aeb46a525c5de487998d68825b7b4e
Tx public key: cb782c1729bdeba1dfdfd98fc2168cd4a2dabbf548eb6d0cb89bd951831a0ef1
Timestamp: 1726754853 Timestamp [UCT]: 2024-09-19 14:07:33 Age [y:d:h:m:s]: 00:157:06:31:49
Block: 1113555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112183 RingCT/type: yes/0
Extra: 01cb782c1729bdeba1dfdfd98fc2168cd4a2dabbf548eb6d0cb89bd951831a0ef1021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b87936c514488746a41973ac5e2d7a7b666dc098f85ced3150c51d28bfaf50e4 0.600000000000 1593270 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": 1113565, "vin": [ { "gen": { "height": 1113555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b87936c514488746a41973ac5e2d7a7b666dc098f85ced3150c51d28bfaf50e4" } } ], "extra": [ 1, 203, 120, 44, 23, 41, 189, 235, 161, 223, 223, 217, 143, 194, 22, 140, 212, 162, 218, 187, 245, 72, 235, 109, 12, 184, 155, 217, 81, 131, 26, 14, 241, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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