Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ffdf4784cac75fc23f80fd0bdd80e6a55e27b8a8c684c0a145c323c01c64613

Tx prefix hash: 9cfdccac2db60be3a2917e82350a17b1982f25bf34b4d111621481d14b71d3be
Tx public key: 5984bae5f7b5b365ed389b0f65163c43f0bbdbf63f0791214ca033f69fbc4f74
Timestamp: 1752626469 Timestamp [UCT]: 2025-07-16 00:41:09 Age [y:d:h:m:s]: 00:175:11:40:54
Block: 1326372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124238 RingCT/type: yes/0
Extra: 015984bae5f7b5b365ed389b0f65163c43f0bbdbf63f0791214ca033f69fbc4f740211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 666509710bfe979f51d0eea53eeaf269a71fa8e157103ed0e14aae6fb5350616 0.600000000000 1814123 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": 1326382, "vin": [ { "gen": { "height": 1326372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "666509710bfe979f51d0eea53eeaf269a71fa8e157103ed0e14aae6fb5350616" } } ], "extra": [ 1, 89, 132, 186, 229, 247, 181, 179, 101, 237, 56, 155, 15, 101, 22, 60, 67, 240, 187, 219, 246, 63, 7, 145, 33, 76, 160, 51, 246, 159, 188, 79, 116, 2, 17, 0, 0, 0, 2, 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