Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc0cd790cb728276f9810c4b68b50dc3488987724d8874556bc4806ae192e122

Tx prefix hash: 47732083a6119517638b9f8a86b774327e0c22ac415e06d8c2463f6c165bbaf3
Tx public key: a510cf1fd2eff7d18fb94099ddd85b0a2f040e7ce7835668ca7e7603d1e649f6
Timestamp: 1722332253 Timestamp [UCT]: 2024-07-30 09:37:33 Age [y:d:h:m:s]: 00:147:15:33:34
Block: 1076896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105643 RingCT/type: yes/0
Extra: 01a510cf1fd2eff7d18fb94099ddd85b0a2f040e7ce7835668ca7e7603d1e649f6021100000007e914dd15000000000000000000

1 output(s) for total of 0.600070000000 dcy

stealth address amount amount idx
00: 44c8d1488422db57de23f04faec6239b32c1b4c04b8d6f5098f6fc1eda89d648 0.600070000000 1549437 of 0

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": 1076906, "vin": [ { "gen": { "height": 1076896 } } ], "vout": [ { "amount": 600070000, "target": { "key": "44c8d1488422db57de23f04faec6239b32c1b4c04b8d6f5098f6fc1eda89d648" } } ], "extra": [ 1, 165, 16, 207, 31, 210, 239, 247, 209, 143, 185, 64, 153, 221, 216, 91, 10, 47, 4, 14, 124, 231, 131, 86, 104, 202, 126, 118, 3, 209, 230, 73, 246, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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