Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01c4329e0fffd083fc4fa9826ff9e7c2133e7e7904b67b744f9ac8efff33d14e

Tx prefix hash: 6439b1ddca2bda49676b20d8f1b13aea55209d9b1d1459120650e0a5805fac12
Tx public key: 1d8d8177dbe803bad29a07e5791aca21f7b62e050fc234a0a2b268302aa1ebf0
Timestamp: 1731783929 Timestamp [UCT]: 2024-11-16 19:05:29 Age [y:d:h:m:s]: 00:177:00:05:50
Block: 1155143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126359 RingCT/type: yes/0
Extra: 011d8d8177dbe803bad29a07e5791aca21f7b62e050fc234a0a2b268302aa1ebf0021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7bb4784c33c9f2c6fa45c29665a754128bcfd8d0633cf2af5bb1be5bea05697 0.600000000000 1640758 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": 1155153, "vin": [ { "gen": { "height": 1155143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7bb4784c33c9f2c6fa45c29665a754128bcfd8d0633cf2af5bb1be5bea05697" } } ], "extra": [ 1, 29, 141, 129, 119, 219, 232, 3, 186, 210, 154, 7, 229, 121, 26, 202, 33, 247, 182, 46, 5, 15, 194, 52, 160, 162, 178, 104, 48, 42, 161, 235, 240, 2, 17, 0, 0, 0, 3, 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