Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b22176d1badb9b2205f71e49461fe7f6d61f7f19d06df1d3b4c2cbe3303a76e

Tx prefix hash: 17d5c30799c125450487a2b88f936d9d11c574ed109a17f323be06ac4c488912
Tx public key: 2fed2bf664c8f45c457de9a36806471812e3ed830f44212d64f170f5ac4c8af7
Timestamp: 1714013691 Timestamp [UCT]: 2024-04-25 02:54:51 Age [y:d:h:m:s]: 01:061:00:30:30
Block: 1007918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304346 RingCT/type: yes/0
Extra: 012fed2bf664c8f45c457de9a36806471812e3ed830f44212d64f170f5ac4c8af7021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f0db0f995770ed607c33ad751dae843c64e0a0aa675fc199ff2f6873be36733 0.600000000000 1469384 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": 1007928, "vin": [ { "gen": { "height": 1007918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f0db0f995770ed607c33ad751dae843c64e0a0aa675fc199ff2f6873be36733" } } ], "extra": [ 1, 47, 237, 43, 246, 100, 200, 244, 92, 69, 125, 233, 163, 104, 6, 71, 24, 18, 227, 237, 131, 15, 68, 33, 45, 100, 241, 112, 245, 172, 76, 138, 247, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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