Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7556a33bcb2728d2700807a0cdbc2d0b4c2fcd8acad7110029aa9184136d52e9

Tx prefix hash: 6052c35d1ef35f6c3c66b7d45943132329cd4ac51e20989c42b444a3ba315b90
Tx public key: c93d4a7b33c9766006e41896c19aec509015cbd0750670067cb8783d6647eb0e
Timestamp: 1718546286 Timestamp [UCT]: 2024-06-16 13:58:06 Age [y:d:h:m:s]: 00:278:17:51:15
Block: 1045519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199174 RingCT/type: yes/0
Extra: 01c93d4a7b33c9766006e41896c19aec509015cbd0750670067cb8783d6647eb0e02110000000136ea7c8b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d0c214ac0f12049fd8c460dc3ab06bb41a9f22917fd8d8794c3942e4e7b8481 0.600000000000 1515110 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": 1045529, "vin": [ { "gen": { "height": 1045519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d0c214ac0f12049fd8c460dc3ab06bb41a9f22917fd8d8794c3942e4e7b8481" } } ], "extra": [ 1, 201, 61, 74, 123, 51, 201, 118, 96, 6, 228, 24, 150, 193, 154, 236, 80, 144, 21, 203, 208, 117, 6, 112, 6, 124, 184, 120, 61, 102, 71, 235, 14, 2, 17, 0, 0, 0, 1, 54, 234, 124, 139, 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