Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eec2af01dc6933ffad8627c77ded17eb1cfdea35f7cedc828fec2d8f2dc3913d

Tx prefix hash: 0c210fbce195d068e66572448e9f209171d5ccd394c52b3d95420fa96a40f5d9
Tx public key: 75f2601ede5d356d0e614953e75a0bac8ae449a0b7f4e8cb16ca71917abda658
Timestamp: 1703578799 Timestamp [UCT]: 2023-12-26 08:19:59 Age [y:d:h:m:s]: 01:100:00:03:43
Block: 921416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332583 RingCT/type: yes/0
Extra: 0175f2601ede5d356d0e614953e75a0bac8ae449a0b7f4e8cb16ca71917abda6580211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5685814a539732f6f11fc458f4ec0af0d2d9460b1b9b1edc563ae7387910f328 0.600000000000 1379104 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": 921426, "vin": [ { "gen": { "height": 921416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5685814a539732f6f11fc458f4ec0af0d2d9460b1b9b1edc563ae7387910f328" } } ], "extra": [ 1, 117, 242, 96, 30, 222, 93, 53, 109, 14, 97, 73, 83, 231, 90, 11, 172, 138, 228, 73, 160, 183, 244, 232, 203, 22, 202, 113, 145, 122, 189, 166, 88, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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