Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a779a7059844b29618b5eb4becf97688f54fcd85792ac5cebe444d7b722dc62

Tx prefix hash: 373d9c171f0424277bcecab9875ed9d538d9f7579746c622f47ae55a73c40c06
Tx public key: 715f13f5394abef8ac04e0d6f36eec1eb8d388e4bf18af1ccdca6039779c8430
Timestamp: 1687740965 Timestamp [UCT]: 2023-06-26 00:56:05 Age [y:d:h:m:s]: 01:344:05:06:28
Block: 790374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507206 RingCT/type: yes/0
Extra: 01715f13f5394abef8ac04e0d6f36eec1eb8d388e4bf18af1ccdca6039779c843002110000001c4b8f5122000000000000000000

1 output(s) for total of 1.476300441000 dcy

stealth address amount amount idx
00: 3da4b1ab24c6fc1f366e8118e6a4d1076fa0df6b47e843c566805c7a6be7c903 1.476300441000 1240701 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": 790384, "vin": [ { "gen": { "height": 790374 } } ], "vout": [ { "amount": 1476300441, "target": { "key": "3da4b1ab24c6fc1f366e8118e6a4d1076fa0df6b47e843c566805c7a6be7c903" } } ], "extra": [ 1, 113, 95, 19, 245, 57, 74, 190, 248, 172, 4, 224, 214, 243, 110, 236, 30, 184, 211, 136, 228, 191, 24, 175, 28, 205, 202, 96, 57, 119, 156, 132, 48, 2, 17, 0, 0, 0, 28, 75, 143, 81, 34, 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