Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee99e39efa635cf08f4d9dd1a263a6b9ac07c2c6b3596623fd56e8da4e363cc6

Tx prefix hash: 7a38854ec17147c63a76f5252154eb458b9f4e14d5fff2beb04d983d29564aae
Tx public key: 7b2f928f7d2f8f7a768be1f895fa5341a161d68a9aaebacbf46933be013fefa1
Timestamp: 1736157009 Timestamp [UCT]: 2025-01-06 09:50:09 Age [y:d:h:m:s]: 00:351:00:23:51
Block: 1191388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248401 RingCT/type: yes/0
Extra: 017b2f928f7d2f8f7a768be1f895fa5341a161d68a9aaebacbf46933be013fefa10211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4638c9ea9fc454b9b256eab51ea6210d00490617e6925f4755718dfa40fe5d6 0.600000000000 1677917 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": 1191398, "vin": [ { "gen": { "height": 1191388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4638c9ea9fc454b9b256eab51ea6210d00490617e6925f4755718dfa40fe5d6" } } ], "extra": [ 1, 123, 47, 146, 143, 125, 47, 143, 122, 118, 139, 225, 248, 149, 250, 83, 65, 161, 97, 214, 138, 154, 174, 186, 203, 244, 105, 51, 190, 1, 63, 239, 161, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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