Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07882540703c63d12619bb2871761a241fef69374fdd20455bce0c448d9094e0

Tx prefix hash: eb8c08db03ebef7e2e372a31154dc06155c325cf75334b4f56a085003ad142e3
Tx public key: ce3ef3a364512ce8afdbfb258babdfdca2a10a3b841753bae6a43e69b26b5def
Timestamp: 1707918458 Timestamp [UCT]: 2024-02-14 13:47:38 Age [y:d:h:m:s]: 01:041:01:13:59
Block: 957382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290359 RingCT/type: yes/0
Extra: 01ce3ef3a364512ce8afdbfb258babdfdca2a10a3b841753bae6a43e69b26b5def0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc9e86caef094d1d646913f8ba45deb87e3e0a7512ec5dc810d043208918c822 0.600000000000 1416700 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": 957392, "vin": [ { "gen": { "height": 957382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc9e86caef094d1d646913f8ba45deb87e3e0a7512ec5dc810d043208918c822" } } ], "extra": [ 1, 206, 62, 243, 163, 100, 81, 44, 232, 175, 219, 251, 37, 139, 171, 223, 220, 162, 161, 10, 59, 132, 23, 83, 186, 230, 164, 62, 105, 178, 107, 93, 239, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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