Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b6323d2586bcb14d631b590e98bb961fd64912500917362d2a42f6a498e6b52

Tx prefix hash: b1acd47b992677be727e49bd2e8152040ab2703ba9d791431e1b3c6a5c094219
Tx public key: 73de7a2adb296839c5c6d204b247e55283622c7904d1d9ddf47a0abe572bbda0
Timestamp: 1695501984 Timestamp [UCT]: 2023-09-23 20:46:24 Age [y:d:h:m:s]: 01:123:14:41:15
Block: 854654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349596 RingCT/type: yes/0
Extra: 0173de7a2adb296839c5c6d204b247e55283622c7904d1d9ddf47a0abe572bbda0021100000005faf35c9c000000000000000000

1 output(s) for total of 0.904016931000 dcy

stealth address amount amount idx
00: 00f9e593f43450e490d3f5cec89640f5f354e8e522d99644ccbdb4fb7db416f5 0.904016931000 1308640 of 0

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": 854664, "vin": [ { "gen": { "height": 854654 } } ], "vout": [ { "amount": 904016931, "target": { "key": "00f9e593f43450e490d3f5cec89640f5f354e8e522d99644ccbdb4fb7db416f5" } } ], "extra": [ 1, 115, 222, 122, 42, 219, 41, 104, 57, 197, 198, 210, 4, 178, 71, 229, 82, 131, 98, 44, 121, 4, 209, 217, 221, 244, 122, 10, 190, 87, 43, 189, 160, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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