Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75f1412a98ffdd5a39da1c9a289dc5362afabdd59eaf1d1d06b1847c7c65ac58

Tx prefix hash: 397ee2640960403591104401927453ad013b32001f30ca97f4574bd9c5002ab8
Tx public key: 79b1c12e9a50f7a27a6c66479b0e6bf8192fff9140a40436e8504275b17caa7e
Timestamp: 1734800590 Timestamp [UCT]: 2024-12-21 17:03:10 Age [y:d:h:m:s]: 00:093:01:58:44
Block: 1180170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66275 RingCT/type: yes/0
Extra: 0179b1c12e9a50f7a27a6c66479b0e6bf8192fff9140a40436e8504275b17caa7e021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c38faeee924f8c812349b932c5ea4f22858d9f7b4829922115cfee9d855019b 0.600000000000 1666575 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": 1180180, "vin": [ { "gen": { "height": 1180170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c38faeee924f8c812349b932c5ea4f22858d9f7b4829922115cfee9d855019b" } } ], "extra": [ 1, 121, 177, 193, 46, 154, 80, 247, 162, 122, 108, 102, 71, 155, 14, 107, 248, 25, 47, 255, 145, 64, 164, 4, 54, 232, 80, 66, 117, 177, 124, 170, 126, 2, 17, 0, 0, 0, 8, 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