Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c942073c290dee83fde98ac35f422dcaf96b119b8eddd4736a0d2376164f7b5f

Tx prefix hash: 84b68d3a3695d90764ac1fd884297868218d9e39d2c3abe62f02e6afc60c50d9
Tx public key: c6afa1dac6cc902f09a46c4f56a0675463d0a92143714881167e6f4b0fd7f53f
Timestamp: 1673912903 Timestamp [UCT]: 2023-01-16 23:48:23 Age [y:d:h:m:s]: 01:345:11:34:43
Block: 676330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507933 RingCT/type: yes/0
Extra: 01c6afa1dac6cc902f09a46c4f56a0675463d0a92143714881167e6f4b0fd7f53f0211000000018b7b6602000000000000000000

1 output(s) for total of 3.524016231000 dcy

stealth address amount amount idx
00: e4b303b16cf7d5c9a09a88ef2ea68f60d7cdc509e2a00ac400a9ae234a451389 3.524016231000 1118039 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": 676340, "vin": [ { "gen": { "height": 676330 } } ], "vout": [ { "amount": 3524016231, "target": { "key": "e4b303b16cf7d5c9a09a88ef2ea68f60d7cdc509e2a00ac400a9ae234a451389" } } ], "extra": [ 1, 198, 175, 161, 218, 198, 204, 144, 47, 9, 164, 108, 79, 86, 160, 103, 84, 99, 208, 169, 33, 67, 113, 72, 129, 22, 126, 111, 75, 15, 215, 245, 63, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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