Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1cabd5a4d34e23b5cb82249921c53b1c66c23fb57df11f57110094d4cc811a6

Tx prefix hash: 2b02660188479f70221cd4d5a68a5f86e6fb675b4d98b48969e52fe3e0009a81
Tx public key: 0ae51e291266a9aadaa76d271591bc34670ddb3711e18cc6c0c147f6c4559852
Timestamp: 1748751796 Timestamp [UCT]: 2025-06-01 04:23:16 Age [y:d:h:m:s]: 00:220:00:22:52
Block: 1295378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154997 RingCT/type: yes/0
Extra: 010ae51e291266a9aadaa76d271591bc34670ddb3711e18cc6c0c147f6c4559852021100000009bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cacb647f16298c7df766143c97696b5e3875884fc0c5d0f40e9613c2a6b8722f 0.600000000000 1782881 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": 1295388, "vin": [ { "gen": { "height": 1295378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cacb647f16298c7df766143c97696b5e3875884fc0c5d0f40e9613c2a6b8722f" } } ], "extra": [ 1, 10, 229, 30, 41, 18, 102, 169, 170, 218, 167, 109, 39, 21, 145, 188, 52, 103, 13, 219, 55, 17, 225, 140, 198, 192, 193, 71, 246, 196, 85, 152, 82, 2, 17, 0, 0, 0, 9, 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