Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b3fac762708a0ac7e3b0302a3e1810e07c766632dba863d5f59936bb66befe1

Tx prefix hash: 898b06c0fbc50df75ebdc100e5bfd6280609fd6bbd0cf679ed119d1a9a5fd055
Tx public key: 5995f5df1fb489bdd05fc9d7224a39a6c80f645614a7fbc7730f29b2a12e5911
Timestamp: 1759791223 Timestamp [UCT]: 2025-10-06 22:53:43 Age [y:d:h:m:s]: 00:093:18:26:29
Block: 1384322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67153 RingCT/type: yes/0
Extra: 015995f5df1fb489bdd05fc9d7224a39a6c80f645614a7fbc7730f29b2a12e591102110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f5eb1f198d9eb8fb251efac3c30b2445cf6e7a24d4096c464475148d775e754 0.600000000000 1872473 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": 1384332, "vin": [ { "gen": { "height": 1384322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f5eb1f198d9eb8fb251efac3c30b2445cf6e7a24d4096c464475148d775e754" } } ], "extra": [ 1, 89, 149, 245, 223, 31, 180, 137, 189, 208, 95, 201, 215, 34, 74, 57, 166, 200, 15, 100, 86, 20, 167, 251, 199, 115, 15, 41, 178, 161, 46, 89, 17, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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