Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64b971e335a976e08912a6e38d34a3c295ba64f9df38e63473124f3b4be5e763

Tx prefix hash: 120d88ec08eb5bf08e08e6ed1a912fe58211dde7d9372d4ec0beb719604868fb
Tx public key: 0989f2863a4869c73b9973e72907a68603d8174d46be14b61753a1ac3f1d4abc
Timestamp: 1752615590 Timestamp [UCT]: 2025-07-15 21:39:50 Age [y:d:h:m:s]: 00:175:10:19:20
Block: 1326286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124194 RingCT/type: yes/0
Extra: 010989f2863a4869c73b9973e72907a68603d8174d46be14b61753a1ac3f1d4abc0211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58114288223ae4797c28dc3f6fc9b8da75ca0c1080336219bf9c4b65d879f844 0.600000000000 1814037 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": 1326296, "vin": [ { "gen": { "height": 1326286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58114288223ae4797c28dc3f6fc9b8da75ca0c1080336219bf9c4b65d879f844" } } ], "extra": [ 1, 9, 137, 242, 134, 58, 72, 105, 199, 59, 153, 115, 231, 41, 7, 166, 134, 3, 216, 23, 77, 70, 190, 20, 182, 23, 83, 161, 172, 63, 29, 74, 188, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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