Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f549131ca88f61161363df71bd49d63291c43a902d2b53d073f91649a8c0e43

Tx prefix hash: 94819d40df895bef088c568fafc02034d025bd8b1ea91c098d0feb13fd414bba
Tx public key: a6e39d576da61449d477c8eda7b817e413d150588341dbd02b5fe2e28b9b9e83
Timestamp: 1674187667 Timestamp [UCT]: 2023-01-20 04:07:47 Age [y:d:h:m:s]: 01:259:02:12:36
Block: 678608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446171 RingCT/type: yes/0
Extra: 01a6e39d576da61449d477c8eda7b817e413d150588341dbd02b5fe2e28b9b9e8302110000000175e3f0e9000000000000000000

1 output(s) for total of 3.463298598000 dcy

stealth address amount amount idx
00: 35a64aa248c9dc7ec5d0da97dcac2a3238ca32fc43e8aa87e1a8b2f236f6aa7e 3.463298598000 1120499 of 0

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": 678618, "vin": [ { "gen": { "height": 678608 } } ], "vout": [ { "amount": 3463298598, "target": { "key": "35a64aa248c9dc7ec5d0da97dcac2a3238ca32fc43e8aa87e1a8b2f236f6aa7e" } } ], "extra": [ 1, 166, 227, 157, 87, 109, 166, 20, 73, 212, 119, 200, 237, 167, 184, 23, 228, 19, 209, 80, 88, 131, 65, 219, 208, 43, 95, 226, 226, 139, 155, 158, 131, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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