Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4b102987f16d584f2f2a967dec3c9f1615170b806de5a48d73187d87607381e

Tx prefix hash: baa682788e86ede5500f28afa4c45c2e1f9d21c0b661657b559ad926cfd3bb0e
Tx public key: 24f8dcd28be5ff9e194be8c28f4a943765f87d876bc7d6b722300df3f5b2b17b
Timestamp: 1749115202 Timestamp [UCT]: 2025-06-05 09:20:02 Age [y:d:h:m:s]: 00:158:15:54:51
Block: 1298395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111062 RingCT/type: yes/0
Extra: 0124f8dcd28be5ff9e194be8c28f4a943765f87d876bc7d6b722300df3f5b2b17b02110000000743846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4823132d62dd9942a078fa9c1d0dce90e8e87793eb0c448e39d98acf356c1668 0.600000000000 1785922 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": 1298405, "vin": [ { "gen": { "height": 1298395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4823132d62dd9942a078fa9c1d0dce90e8e87793eb0c448e39d98acf356c1668" } } ], "extra": [ 1, 36, 248, 220, 210, 139, 229, 255, 158, 25, 75, 232, 194, 143, 74, 148, 55, 101, 248, 125, 135, 107, 199, 214, 183, 34, 48, 13, 243, 245, 178, 177, 123, 2, 17, 0, 0, 0, 7, 67, 132, 109, 102, 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