Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe801299a5343d269d113a54e9ed6f5f462496c309ba200f78489942078c176c

Tx prefix hash: 8ac52334e3154180082193fc3bd87b1ae05b91a57b69bbb7297462b270d4913c
Tx public key: 1f46931e18d5e8a2a137bfdb871a917c82644e40adaf24993f57ad93e7eeff30
Timestamp: 1578538547 Timestamp [UCT]: 2020-01-09 02:55:47 Age [y:d:h:m:s]: 04:302:07:31:39
Block: 41730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105299 RingCT/type: yes/0
Extra: 011f46931e18d5e8a2a137bfdb871a917c82644e40adaf24993f57ad93e7eeff3002110000000a8a2ee0d9000000000000000000

1 output(s) for total of 446.417745001000 dcy

stealth address amount amount idx
00: 4ff10614873eeea9eb59a685fb7169458a848fb69fa8b0f8a2f7f3211e37ddb9 446.417745001000 74651 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": 41740, "vin": [ { "gen": { "height": 41730 } } ], "vout": [ { "amount": 446417745001, "target": { "key": "4ff10614873eeea9eb59a685fb7169458a848fb69fa8b0f8a2f7f3211e37ddb9" } } ], "extra": [ 1, 31, 70, 147, 30, 24, 213, 232, 162, 161, 55, 191, 219, 135, 26, 145, 124, 130, 100, 78, 64, 173, 175, 36, 153, 63, 87, 173, 147, 231, 238, 255, 48, 2, 17, 0, 0, 0, 10, 138, 46, 224, 217, 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