Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f56ad65d4b60ca5ac64a43d2deebba8a97c01eb19d15bfa5ca984d977e19685

Tx prefix hash: 99b8cce8030dce57a070787f61448739fdf650d0bf748d9c03dc902a36919ce6
Tx public key: bd40fe4200a4b4226c5b325bb284cf5108db25c0c89a14a19d19ab22d01786a6
Timestamp: 1705062131 Timestamp [UCT]: 2024-01-12 12:22:11 Age [y:d:h:m:s]: 01:041:07:51:21
Block: 933700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290593 RingCT/type: yes/0
Extra: 01bd40fe4200a4b4226c5b325bb284cf5108db25c0c89a14a19d19ab22d01786a60211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2385355fc878f7b128d6fcb468841fbc8f3f64f74f432c156d8ee9e4e01f39c9 0.600000000000 1391670 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": 933710, "vin": [ { "gen": { "height": 933700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2385355fc878f7b128d6fcb468841fbc8f3f64f74f432c156d8ee9e4e01f39c9" } } ], "extra": [ 1, 189, 64, 254, 66, 0, 164, 180, 34, 108, 91, 50, 91, 178, 132, 207, 81, 8, 219, 37, 192, 200, 154, 20, 161, 157, 25, 171, 34, 208, 23, 134, 166, 2, 17, 0, 0, 0, 5, 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