Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edd2ea1c07b1b49a34cd916c53475c5b29c0a98e10ace65e03c53d8bd54da610

Tx prefix hash: 621f15b23402c4206841a81f2a41c2ab486b856b5ac6885c3d5f5372d44369de
Tx public key: 0b58510f896108ec56ab906f60e303550a362afbe75479154181f4acf3ef525d
Timestamp: 1731515459 Timestamp [UCT]: 2024-11-13 16:30:59 Age [y:d:h:m:s]: 00:128:22:29:58
Block: 1152931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91974 RingCT/type: yes/0
Extra: 010b58510f896108ec56ab906f60e303550a362afbe75479154181f4acf3ef525d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54dff6afa9c5a4c54024d68b89fdf91c2257bb5c04a3d362b2cf24037d7efbed 0.600000000000 1638538 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": 1152941, "vin": [ { "gen": { "height": 1152931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54dff6afa9c5a4c54024d68b89fdf91c2257bb5c04a3d362b2cf24037d7efbed" } } ], "extra": [ 1, 11, 88, 81, 15, 137, 97, 8, 236, 86, 171, 144, 111, 96, 227, 3, 85, 10, 54, 42, 251, 231, 84, 121, 21, 65, 129, 244, 172, 243, 239, 82, 93, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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