Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0137eb9060f38c12e7402282d9afd2a637ed458dbcd43d8e7105bd204c878286

Tx prefix hash: 3a9e0238c00898ee330ad1a841671df18cfe49a191fb94599db852406a12a22c
Tx public key: 8beb42575960b842971e0fb09a63c88086120730e03df8aa6e8928f806a14674
Timestamp: 1716633149 Timestamp [UCT]: 2024-05-25 10:32:29 Age [y:d:h:m:s]: 01:011:05:47:18
Block: 1029661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268952 RingCT/type: yes/0
Extra: 018beb42575960b842971e0fb09a63c88086120730e03df8aa6e8928f806a1467402110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6ae44c1c6393a160d0a4f3d28772b246c19f48df04865bdcdd9f626371a79a1 0.600000000000 1497810 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": 1029671, "vin": [ { "gen": { "height": 1029661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6ae44c1c6393a160d0a4f3d28772b246c19f48df04865bdcdd9f626371a79a1" } } ], "extra": [ 1, 139, 235, 66, 87, 89, 96, 184, 66, 151, 30, 15, 176, 154, 99, 200, 128, 134, 18, 7, 48, 224, 61, 248, 170, 110, 137, 40, 248, 6, 161, 70, 116, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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