Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11fdf1deeea06d8e69856824676c92ff6eac8c1992e80fd8a9bdf3dea5d98c3c

Tx prefix hash: e1f84e550562ca930993c69296e4fbc9e0e32e2093904b98a88c159f3ec77eff
Tx public key: acb60fea6f8a99f2138ecd094f66ae55f56ec94d0969aea47ddc29b3e9a514bd
Timestamp: 1764036047 Timestamp [UCT]: 2025-11-25 02:00:47 Age [y:d:h:m:s]: 00:035:18:48:46
Block: 1419508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25618 RingCT/type: yes/0
Extra: 01acb60fea6f8a99f2138ecd094f66ae55f56ec94d0969aea47ddc29b3e9a514bd021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dfaa08dfcd9f1021615e7623a7ead809ff7058f1c6b7d427a47f4afc17576f6 0.600000000000 1908045 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": 1419518, "vin": [ { "gen": { "height": 1419508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dfaa08dfcd9f1021615e7623a7ead809ff7058f1c6b7d427a47f4afc17576f6" } } ], "extra": [ 1, 172, 182, 15, 234, 111, 138, 153, 242, 19, 142, 205, 9, 79, 102, 174, 85, 245, 110, 201, 77, 9, 105, 174, 164, 125, 220, 41, 179, 233, 165, 20, 189, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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