Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9af7c6e735b84b913b399c4ecbf99101bdc3707b5a0d100b9ec1f3df911fc30

Tx prefix hash: afc9bee034fe1470ecdb39f4784e8466f934c3b85d3826e881c47e0597b9d1d4
Tx public key: 3a1d55f805675d7e4bde6fdb250ed18c0f9c4266e7a0c25d27af3d1c5270ea30
Timestamp: 1713366620 Timestamp [UCT]: 2024-04-17 15:10:20 Age [y:d:h:m:s]: 01:200:04:23:51
Block: 1002557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401719 RingCT/type: yes/0
Extra: 013a1d55f805675d7e4bde6fdb250ed18c0f9c4266e7a0c25d27af3d1c5270ea300211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 448075dea39b16a0315555e00de9328bd1234011d5195a9d4d87954d491f99f1 0.600000000000 1463073 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": 1002567, "vin": [ { "gen": { "height": 1002557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "448075dea39b16a0315555e00de9328bd1234011d5195a9d4d87954d491f99f1" } } ], "extra": [ 1, 58, 29, 85, 248, 5, 103, 93, 126, 75, 222, 111, 219, 37, 14, 209, 140, 15, 156, 66, 102, 231, 160, 194, 93, 39, 175, 61, 28, 82, 112, 234, 48, 2, 17, 0, 0, 0, 1, 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