Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3be36b61a55d20b2b514f28950f7e64d4518135cde05a4b3f0cb21cdbaa75312

Tx prefix hash: 372589f7a66ea59e4c9dded621bfc85187ce36a2611d74cb8d3b9f20772d8080
Tx public key: c16db78c2638c9d80bbfd97607248f214425d521bd80ba0ba58bbbd2a20fc8f2
Timestamp: 1703758584 Timestamp [UCT]: 2023-12-28 10:16:24 Age [y:d:h:m:s]: 01:169:19:35:05
Block: 922900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382434 RingCT/type: yes/0
Extra: 01c16db78c2638c9d80bbfd97607248f214425d521bd80ba0ba58bbbd2a20fc8f202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b0c61e745bb1f7e7cc25699156be3e67a6cff0dbc26483ce56a20470f5f040b 0.600000000000 1380606 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": 922910, "vin": [ { "gen": { "height": 922900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b0c61e745bb1f7e7cc25699156be3e67a6cff0dbc26483ce56a20470f5f040b" } } ], "extra": [ 1, 193, 109, 183, 140, 38, 56, 201, 216, 11, 191, 217, 118, 7, 36, 143, 33, 68, 37, 213, 33, 189, 128, 186, 11, 165, 139, 187, 210, 162, 15, 200, 242, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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