Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03b01323f69121b313ae50e796c7f79127808a4a80239014f7d97000819adb25

Tx prefix hash: e650d341086dbdbce9f1fb4bc59c507d2aa66229dcd3ee58cd8d3f049821ac52
Tx public key: f3bbdf73aaa0ef5f031697055d5ee3efeb04b50e8b89aaec1942b43da1c3a971
Timestamp: 1721669705 Timestamp [UCT]: 2024-07-22 17:35:05 Age [y:d:h:m:s]: 00:255:08:44:04
Block: 1071387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182424 RingCT/type: yes/0
Extra: 01f3bbdf73aaa0ef5f031697055d5ee3efeb04b50e8b89aaec1942b43da1c3a971021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7671405fd2233a92b7c6f4b3c5106591ce4254f3fce951641a3ae7bb9fbd2cca 0.600000000000 1543600 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": 1071397, "vin": [ { "gen": { "height": 1071387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7671405fd2233a92b7c6f4b3c5106591ce4254f3fce951641a3ae7bb9fbd2cca" } } ], "extra": [ 1, 243, 187, 223, 115, 170, 160, 239, 95, 3, 22, 151, 5, 93, 94, 227, 239, 235, 4, 181, 14, 139, 137, 170, 236, 25, 66, 180, 61, 161, 195, 169, 113, 2, 17, 0, 0, 0, 6, 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