Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a0cdc6231b55f2a8c5fb691fe8de09692b2e319737cf20ae57f734ed2f1c079

Tx prefix hash: 443700160b0dffaf0d6c86be7bb4c14fbd9ba6e5d5b9a964d8ad45834033abdc
Tx public key: 1a77a795df8eb009d4114c89fe403c90b34b16614bac68651213c4c07512bf75
Timestamp: 1708241025 Timestamp [UCT]: 2024-02-18 07:23:45 Age [y:d:h:m:s]: 01:005:23:20:40
Block: 960062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265256 RingCT/type: yes/0
Extra: 011a77a795df8eb009d4114c89fe403c90b34b16614bac68651213c4c07512bf750211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8640861c4357f265a4a11886bc2d3835ba152acb95d4647a763ee87a5bba3d7d 0.600000000000 1419621 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": 960072, "vin": [ { "gen": { "height": 960062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8640861c4357f265a4a11886bc2d3835ba152acb95d4647a763ee87a5bba3d7d" } } ], "extra": [ 1, 26, 119, 167, 149, 223, 142, 176, 9, 212, 17, 76, 137, 254, 64, 60, 144, 179, 75, 22, 97, 75, 172, 104, 101, 18, 19, 196, 192, 117, 18, 191, 117, 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