Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dae2ff15f4d9024a8cb8366bcf325159c8ef21f2c65afc48b87ae794ac2ed729

Tx prefix hash: d1585a76b22d28a51586d0e30cffb602c835a2d9164a9d6b540818a7ac55721a
Tx public key: f36c380123e7d3d93492ec4b758eef2f2870e09039388e1301b22f6fd7cf71a3
Timestamp: 1754895966 Timestamp [UCT]: 2025-08-11 07:06:06 Age [y:d:h:m:s]: 00:134:18:29:32
Block: 1344653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95598 RingCT/type: yes/0
Extra: 01f36c380123e7d3d93492ec4b758eef2f2870e09039388e1301b22f6fd7cf71a3021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbaf729e3fbada7806c7a761569cfa34576b6f2e1fe76c789666daacc143d6d1 0.600000000000 1832538 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": 1344663, "vin": [ { "gen": { "height": 1344653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbaf729e3fbada7806c7a761569cfa34576b6f2e1fe76c789666daacc143d6d1" } } ], "extra": [ 1, 243, 108, 56, 1, 35, 231, 211, 217, 52, 146, 236, 75, 117, 142, 239, 47, 40, 112, 224, 144, 57, 56, 142, 19, 1, 178, 47, 111, 215, 207, 113, 163, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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