Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22239bef5f41e0b629c62d7009d781764167ad3dff467c2b6272011d79e214fc

Tx prefix hash: ecf6810588d8b0f36c55784b99c4c19cd783668424af602a0dcc149b38280acd
Tx public key: d7fd589065b2cc81cae00d00972dfc8147d903aebcb6ec9ad963c4f5970ced9e
Timestamp: 1723727295 Timestamp [UCT]: 2024-08-15 13:08:15 Age [y:d:h:m:s]: 00:258:21:21:49
Block: 1088461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184909 RingCT/type: yes/0
Extra: 01d7fd589065b2cc81cae00d00972dfc8147d903aebcb6ec9ad963c4f5970ced9e021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f645dd10a0bc0ceda0f33de34acd8da4b5e1b25033da0eab2824c2b45461a4a 0.600000000000 1563078 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": 1088471, "vin": [ { "gen": { "height": 1088461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f645dd10a0bc0ceda0f33de34acd8da4b5e1b25033da0eab2824c2b45461a4a" } } ], "extra": [ 1, 215, 253, 88, 144, 101, 178, 204, 129, 202, 224, 13, 0, 151, 45, 252, 129, 71, 217, 3, 174, 188, 182, 236, 154, 217, 99, 196, 245, 151, 12, 237, 158, 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