Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0094919da68a77a52545cc86ad61ad069338e07fdccafca53b469e19b3a2bf96

Tx prefix hash: 24bd96552e3a91848cd8222f9db551e0a9bfa17daee1a82fd5cf7e66f7d1bdd2
Tx public key: 61cd8683d58efa2d411225ca68e7a57a6d3cfd285b9b354fd2fddd5eb2c419f7
Timestamp: 1708474113 Timestamp [UCT]: 2024-02-21 00:08:33 Age [y:d:h:m:s]: 01:102:22:04:16
Block: 961994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334632 RingCT/type: yes/0
Extra: 0161cd8683d58efa2d411225ca68e7a57a6d3cfd285b9b354fd2fddd5eb2c419f70211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c9488a94138175853fbe7e4f9cc7cb6ab8e60465ab2945b291bdfb24badc446 0.600000000000 1421617 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": 962004, "vin": [ { "gen": { "height": 961994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c9488a94138175853fbe7e4f9cc7cb6ab8e60465ab2945b291bdfb24badc446" } } ], "extra": [ 1, 97, 205, 134, 131, 213, 142, 250, 45, 65, 18, 37, 202, 104, 231, 165, 122, 109, 60, 253, 40, 91, 155, 53, 79, 210, 253, 221, 94, 178, 196, 25, 247, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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