Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bf11a508fa24913adc53da644c0a05e673013d529c34b1c0ca2c1844698438d

Tx prefix hash: ae4c05637523665da4a33cf44d81c871e90d711ccbed68245485df8e94cbcd37
Tx public key: 0e7a387faf4bce0fd5ef63ead8cfc57e3fc2c74210d0e9e53edbc77181a793a9
Timestamp: 1751025401 Timestamp [UCT]: 2025-06-27 11:56:41 Age [y:d:h:m:s]: 00:146:05:47:44
Block: 1313833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102556 RingCT/type: yes/0
Extra: 010e7a387faf4bce0fd5ef63ead8cfc57e3fc2c74210d0e9e53edbc77181a793a902110000000abf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70a35016379f1b3f5a4e09da707b429c462ae56c05530115e6a1d75b5969c334 0.600000000000 1801476 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": 1313843, "vin": [ { "gen": { "height": 1313833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70a35016379f1b3f5a4e09da707b429c462ae56c05530115e6a1d75b5969c334" } } ], "extra": [ 1, 14, 122, 56, 127, 175, 75, 206, 15, 213, 239, 99, 234, 216, 207, 197, 126, 63, 194, 199, 66, 16, 208, 233, 229, 62, 219, 199, 113, 129, 167, 147, 169, 2, 17, 0, 0, 0, 10, 191, 81, 178, 162, 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