Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c96c3ca39f7277c8e82079ffe4053db7b6d29868aa33775842ab5fe7f7cd0a3

Tx prefix hash: ecaa578b013467642f5bd81452e97a72445c3f67b0bc99e9a0260d0433a6c95a
Tx public key: b50fea2170101f59a99bf3197c2a21f57febd02fb30fcf5c26ae41612a1dfb7b
Timestamp: 1738008039 Timestamp [UCT]: 2025-01-27 20:00:39 Age [y:d:h:m:s]: 00:140:20:44:58
Block: 1206448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100624 RingCT/type: yes/0
Extra: 01b50fea2170101f59a99bf3197c2a21f57febd02fb30fcf5c26ae41612a1dfb7b0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97231457436f92368801ddd2adba5be06f8341c9da23cb146a7fa92f769311c0 0.600000000000 1693153 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": 1206458, "vin": [ { "gen": { "height": 1206448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97231457436f92368801ddd2adba5be06f8341c9da23cb146a7fa92f769311c0" } } ], "extra": [ 1, 181, 15, 234, 33, 112, 16, 31, 89, 169, 155, 243, 25, 124, 42, 33, 245, 127, 235, 208, 47, 179, 15, 207, 92, 38, 174, 65, 97, 42, 29, 251, 123, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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