Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fdd26903c0786aaf707898ac1190b6d78662eee3fdca918310927a6d4fbb904

Tx prefix hash: 690f5a693e9542ea5448af5cc5c670e218987fe9a8e01ada915aec080c31de37
Tx public key: 10d2e9b064d2923b5d86a237223dbf7192d99c61481cacc6adb4464765601a8e
Timestamp: 1686446287 Timestamp [UCT]: 2023-06-11 01:18:07 Age [y:d:h:m:s]: 01:294:04:24:56
Block: 779642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471416 RingCT/type: yes/0
Extra: 0110d2e9b064d2923b5d86a237223dbf7192d99c61481cacc6adb4464765601a8e021100000003faf35c9c000000000000000000

1 output(s) for total of 1.602221551000 dcy

stealth address amount amount idx
00: da9b0fcdef41632f4847a9344fed926e5823fc0afd1aa529a1ba98e9df384792 1.602221551000 1229311 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": 779652, "vin": [ { "gen": { "height": 779642 } } ], "vout": [ { "amount": 1602221551, "target": { "key": "da9b0fcdef41632f4847a9344fed926e5823fc0afd1aa529a1ba98e9df384792" } } ], "extra": [ 1, 16, 210, 233, 176, 100, 210, 146, 59, 93, 134, 162, 55, 34, 61, 191, 113, 146, 217, 156, 97, 72, 28, 172, 198, 173, 180, 70, 71, 101, 96, 26, 142, 2, 17, 0, 0, 0, 3, 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