Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4156545f8a0ffeec7375fcdb2fc9e379094a2efcc9a91ca8ee301ad0002af6a

Tx prefix hash: 11ff33f3f6d2e7ea7e0337328750ca0dad7b3a28769aacfa57780a57674bb085
Tx public key: 34fbe54ffbdaeb37ee65f674454c59184832e2383d9b2460d15fd46dbdc6ae7d
Timestamp: 1657066238 Timestamp [UCT]: 2022-07-06 00:10:38 Age [y:d:h:m:s]: 02:302:15:44:49
Block: 537517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 737454 RingCT/type: yes/0
Extra: 0134fbe54ffbdaeb37ee65f674454c59184832e2383d9b2460d15fd46dbdc6ae7d021100000001a8c141c5000000000000000000

1 output(s) for total of 10.162093714000 dcy

stealth address amount amount idx
00: 7a284f13c7811face2cc64ae08894df61eb6d1ca384f0a243702325a8928101a 10.162093714000 967408 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": 537527, "vin": [ { "gen": { "height": 537517 } } ], "vout": [ { "amount": 10162093714, "target": { "key": "7a284f13c7811face2cc64ae08894df61eb6d1ca384f0a243702325a8928101a" } } ], "extra": [ 1, 52, 251, 229, 79, 251, 218, 235, 55, 238, 101, 246, 116, 69, 76, 89, 24, 72, 50, 226, 56, 61, 155, 36, 96, 209, 95, 212, 109, 189, 198, 174, 125, 2, 17, 0, 0, 0, 1, 168, 193, 65, 197, 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