Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ea7703591bdf5343f3881935eb22b608dae093819c8c7bbc18acc5ba3af0f3f

Tx prefix hash: 3ee6e39994043603ddc2a7c6da10fbfc879d1b31470d6f53829a7fe318a233ed
Tx public key: b6c1f2e321387131c4c1c32646b6e8134e18c5f627dc86db3477ffb0e68b2703
Timestamp: 1748293991 Timestamp [UCT]: 2025-05-26 21:13:11 Age [y:d:h:m:s]: 00:250:12:52:40
Block: 1291589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176666 RingCT/type: yes/0
Extra: 01b6c1f2e321387131c4c1c32646b6e8134e18c5f627dc86db3477ffb0e68b2703021100000006523560da000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e4f92fa1c6be152ce2a97e95a82113c28a10040c95c5746b46157ea9ee6674b 0.600000000000 1779060 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": 1291599, "vin": [ { "gen": { "height": 1291589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e4f92fa1c6be152ce2a97e95a82113c28a10040c95c5746b46157ea9ee6674b" } } ], "extra": [ 1, 182, 193, 242, 227, 33, 56, 113, 49, 196, 193, 195, 38, 70, 182, 232, 19, 78, 24, 197, 246, 39, 220, 134, 219, 52, 119, 255, 176, 230, 139, 39, 3, 2, 17, 0, 0, 0, 6, 82, 53, 96, 218, 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