Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b65d4002760003bcea0068240ce10373f84f39d416e676546a885b0c9250a11

Tx prefix hash: 47730fc9ba89ad5ac8db49c71a3842385a8a3e82f5966f9eae09374206cb8ae4
Tx public key: 749d022d9945cab38f47401a5b4f9e5923e8cda2ea31202a74f55268e322e9d4
Timestamp: 1754427497 Timestamp [UCT]: 2025-08-05 20:58:17 Age [y:d:h:m:s]: 00:075:22:50:23
Block: 1341023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53261 RingCT/type: yes/0
Extra: 01749d022d9945cab38f47401a5b4f9e5923e8cda2ea31202a74f55268e322e9d4021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba725ee94669bec1292d3089dc631ca211c0439b523a4eb307b3bcde2a388d5f 0.600000000000 1828844 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": 1341033, "vin": [ { "gen": { "height": 1341023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba725ee94669bec1292d3089dc631ca211c0439b523a4eb307b3bcde2a388d5f" } } ], "extra": [ 1, 116, 157, 2, 45, 153, 69, 202, 179, 143, 71, 64, 26, 91, 79, 158, 89, 35, 232, 205, 162, 234, 49, 32, 42, 116, 245, 82, 104, 227, 34, 233, 212, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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