Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e290a20295c0ebc1c1ad5a3b9590bbe947a1f40be108539855da6320f2ad9c02

Tx prefix hash: 189b1186b6dfdacc7c5b919bfab92c840b1d4478bd0633639cd7c9a71fc45dba
Tx public key: 151e2da3aea893312098294b96db39758c7953aae5f5cdea79f3811eec679a2e
Timestamp: 1635308433 Timestamp [UCT]: 2021-10-27 04:20:33 Age [y:d:h:m:s]: 03:064:10:14:04
Block: 361321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 824451 RingCT/type: yes/0
Extra: 01151e2da3aea893312098294b96db39758c7953aae5f5cdea79f3811eec679a2e021100000001328bb496000000000000000000

1 output(s) for total of 38.977701679000 dcy

stealth address amount amount idx
00: 5cb438d4f3d3de2c9809f2cb73e29f91bfacd44b2415ad2525ed757071dd06c5 38.977701679000 735140 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": 361331, "vin": [ { "gen": { "height": 361321 } } ], "vout": [ { "amount": 38977701679, "target": { "key": "5cb438d4f3d3de2c9809f2cb73e29f91bfacd44b2415ad2525ed757071dd06c5" } } ], "extra": [ 1, 21, 30, 45, 163, 174, 168, 147, 49, 32, 152, 41, 75, 150, 219, 57, 117, 140, 121, 83, 170, 229, 245, 205, 234, 121, 243, 129, 30, 236, 103, 154, 46, 2, 17, 0, 0, 0, 1, 50, 139, 180, 150, 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