Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ebccb088fdf66be3fa095327b4ff0a380b76480dcb5cf7d9f6424908299bd3b

Tx prefix hash: 64c1481a7dc266ab2fede72b6cdf920452dcb43a5a4c778ddb60c9120394b5ef
Tx public key: 8ea804e4a3feba7f912957a1e6fcb0e53ff6a225ba8db02b46c6ef9c8786571d
Timestamp: 1756177944 Timestamp [UCT]: 2025-08-26 03:12:24 Age [y:d:h:m:s]: 00:136:05:15:08
Block: 1354559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97369 RingCT/type: yes/0
Extra: 018ea804e4a3feba7f912957a1e6fcb0e53ff6a225ba8db02b46c6ef9c8786571d0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 201bcb2860b72624556b1b184311501f816730671bb40ff65262d53d23bd3e66 0.600000000000 1842548 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": 1354569, "vin": [ { "gen": { "height": 1354559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "201bcb2860b72624556b1b184311501f816730671bb40ff65262d53d23bd3e66" } } ], "extra": [ 1, 142, 168, 4, 228, 163, 254, 186, 127, 145, 41, 87, 161, 230, 252, 176, 229, 63, 246, 162, 37, 186, 141, 176, 43, 70, 198, 239, 156, 135, 134, 87, 29, 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