Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b07ea20c491b2b67c90cfc564e22781062153559d25cfad4938a7540b6c6bbed

Tx prefix hash: b393b8a6738e172b1b85c8da328860d9c60a8d7b08c8494a3c4f842068c2296d
Tx public key: 55873a1ea999749fe038d28ac7d49a4fe5d6e28917cd9f8ce00d891d9741d0b3
Timestamp: 1756011536 Timestamp [UCT]: 2025-08-24 04:58:56 Age [y:d:h:m:s]: 00:094:09:25:21
Block: 1353184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67407 RingCT/type: yes/0
Extra: 0155873a1ea999749fe038d28ac7d49a4fe5d6e28917cd9f8ce00d891d9741d0b3021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bb019d2730828d6e3061e41d47b3c9cd2c60c344780479ceaff9f3651d1e73d 0.600000000000 1841157 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": 1353194, "vin": [ { "gen": { "height": 1353184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bb019d2730828d6e3061e41d47b3c9cd2c60c344780479ceaff9f3651d1e73d" } } ], "extra": [ 1, 85, 135, 58, 30, 169, 153, 116, 159, 224, 56, 210, 138, 199, 212, 154, 79, 229, 214, 226, 137, 23, 205, 159, 140, 224, 13, 137, 29, 151, 65, 208, 179, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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