Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d758e87d1091d4b8fd6f1a00856d35b07fd868017220720cd4c64ee4c01b71a1

Tx prefix hash: 6bc19b5e488e651ee4870437c3ac7f8aad535edc59cc9315cc266679c54671dd
Tx public key: 2a13b78c02ce3a30692ef6d233d263275d08651717f8af82d13c87f065027769
Timestamp: 1574093557 Timestamp [UCT]: 2019-11-18 16:12:37 Age [y:d:h:m:s]: 05:349:02:17:22
Block: 11737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1390370 RingCT/type: yes/0
Extra: 012a13b78c02ce3a30692ef6d233d263275d08651717f8af82d13c87f065027769021100000003ccefb800000000000000000000

1 output(s) for total of 561.191824655000 dcy

stealth address amount amount idx
00: 09e94a7dd6baf9ada6b9c7a2fd9eff2fc290791b9be59e9859e4ca7ac004081d 561.191824655000 12816 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": 11747, "vin": [ { "gen": { "height": 11737 } } ], "vout": [ { "amount": 561191824655, "target": { "key": "09e94a7dd6baf9ada6b9c7a2fd9eff2fc290791b9be59e9859e4ca7ac004081d" } } ], "extra": [ 1, 42, 19, 183, 140, 2, 206, 58, 48, 105, 46, 246, 210, 51, 210, 99, 39, 93, 8, 101, 23, 23, 248, 175, 130, 209, 60, 135, 240, 101, 2, 119, 105, 2, 17, 0, 0, 0, 3, 204, 239, 184, 0, 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