Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4af67b24fd9e065e238c7a8975092035de36472e0f0bd6462efd670937b3fa70

Tx prefix hash: f853d4401702ac64ac550e7ae606b9b37b5d3cb19707e4e9a19a13ce73ba8b78
Tx public key: 2b3ff37254ed7a84e3ba78a13025d0d3876fbb130793bb2a1824e5a53fc846f1
Timestamp: 1721711218 Timestamp [UCT]: 2024-07-23 05:06:58 Age [y:d:h:m:s]: 00:191:14:03:59
Block: 1071735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136818 RingCT/type: yes/0
Extra: 012b3ff37254ed7a84e3ba78a13025d0d3876fbb130793bb2a1824e5a53fc846f1021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfedc052c0ebb6e6645c2b79f3f0465515dc26567683a825a7129a9724f20b99 0.600000000000 1544070 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": 1071745, "vin": [ { "gen": { "height": 1071735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfedc052c0ebb6e6645c2b79f3f0465515dc26567683a825a7129a9724f20b99" } } ], "extra": [ 1, 43, 63, 243, 114, 84, 237, 122, 132, 227, 186, 120, 161, 48, 37, 208, 211, 135, 111, 187, 19, 7, 147, 187, 42, 24, 36, 229, 165, 63, 200, 70, 241, 2, 17, 0, 0, 0, 4, 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