Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5234bc4597f14e4f463232e9c5b340235549a1f0d8019da0c3336bc9f55c3c0

Tx prefix hash: f0a1ec18bcdd07319f5cd3fb37eb23fb350a30f96deb1ec2fe957a290310d22f
Tx public key: 26d1db95d3d7f4945cf20139d5c4178f15ea285d66484ff209302e2d0f32c9b9
Timestamp: 1763060046 Timestamp [UCT]: 2025-11-13 18:54:06 Age [y:d:h:m:s]: 00:040:09:43:58
Block: 1411415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28925 RingCT/type: yes/0
Extra: 0126d1db95d3d7f4945cf20139d5c4178f15ea285d66484ff209302e2d0f32c9b90211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e2c9c14a4c43373990b67d57ad7f919b0784a83999c9090eae865496411071e 0.600000000000 1899876 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": 1411425, "vin": [ { "gen": { "height": 1411415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e2c9c14a4c43373990b67d57ad7f919b0784a83999c9090eae865496411071e" } } ], "extra": [ 1, 38, 209, 219, 149, 211, 215, 244, 148, 92, 242, 1, 57, 213, 196, 23, 143, 21, 234, 40, 93, 102, 72, 79, 242, 9, 48, 46, 45, 15, 50, 201, 185, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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