Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb661dd21f3521027884d50342e5cc7c8fdb02ec9d71862b183af11cfcb61136

Tx prefix hash: 0caaa54266d7fd92ee32f3932f0f2f6bb817b70cc0b36bfb396b877c28dbdbfc
Tx public key: b21a136debe905ea6160eda89a457816449266e0b6948fae207000a9d5a12ed9
Timestamp: 1582443460 Timestamp [UCT]: 2020-02-23 07:37:40 Age [y:d:h:m:s]: 05:011:02:00:56
Block: 70840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161027 RingCT/type: yes/0
Extra: 01b21a136debe905ea6160eda89a457816449266e0b6948fae207000a9d5a12ed9021100000001026b59f3000000000000000000

1 output(s) for total of 357.501999684000 dcy

stealth address amount amount idx
00: 27d5c0104f207f76e1af26d7477855e98d4c6c4bc3e4aaa692c5169d4f39b1d5 357.501999684000 130860 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": 70850, "vin": [ { "gen": { "height": 70840 } } ], "vout": [ { "amount": 357501999684, "target": { "key": "27d5c0104f207f76e1af26d7477855e98d4c6c4bc3e4aaa692c5169d4f39b1d5" } } ], "extra": [ 1, 178, 26, 19, 109, 235, 233, 5, 234, 97, 96, 237, 168, 154, 69, 120, 22, 68, 146, 102, 224, 182, 148, 143, 174, 32, 112, 0, 169, 213, 161, 46, 217, 2, 17, 0, 0, 0, 1, 2, 107, 89, 243, 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