Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7285dc9008a325574117b3c9ab967fbd5e75c91af7a2b4568e334f8f166ee78

Tx prefix hash: 21f3bcb89022aa0549c7223fbf4d0cd78f32f5059ba95474369c4163a509c8de
Tx public key: 08d15580678949f809b0f3f37c907d83828a5d7049acef80f28f0aad001d96ae
Timestamp: 1702286796 Timestamp [UCT]: 2023-12-11 09:26:36 Age [y:d:h:m:s]: 01:331:13:46:53
Block: 910705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495820 RingCT/type: yes/0
Extra: 0108d15580678949f809b0f3f37c907d83828a5d7049acef80f28f0aad001d96ae021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecd1633c8c8a717ddab6dc2a6b1933d67f6f5b9bae633b51f1b534b27529094a 0.600000000000 1367872 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": 910715, "vin": [ { "gen": { "height": 910705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecd1633c8c8a717ddab6dc2a6b1933d67f6f5b9bae633b51f1b534b27529094a" } } ], "extra": [ 1, 8, 209, 85, 128, 103, 137, 73, 248, 9, 176, 243, 243, 124, 144, 125, 131, 130, 138, 93, 112, 73, 172, 239, 128, 242, 143, 10, 173, 0, 29, 150, 174, 2, 17, 0, 0, 0, 5, 230, 210, 127, 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