Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 683fa5252f991180b63193b1191b2b71d6f20a1487a29e5f34395af4148c4033

Tx prefix hash: 37b8764df1c054616e707c2098d5c30f83fcb3977c3c60562f8887f80a985c6d
Tx public key: 9e9a1bf91e860e2c8f3a48c20c6b59eace81de21ed5ede687019fffb2c241190
Timestamp: 1587538145 Timestamp [UCT]: 2020-04-22 06:49:05 Age [y:d:h:m:s]: 04:361:09:58:55
Block: 95281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168260 RingCT/type: yes/0
Extra: 019e9a1bf91e860e2c8f3a48c20c6b59eace81de21ed5ede687019fffb2c241190021100000477a86a1a65000000000000000000

1 output(s) for total of 296.684776105000 dcy

stealth address amount amount idx
00: 17d2b9d1538a4e8c35bcff9383c051dcaced5dd4545e1a4abe9b38a805329cdd 296.684776105000 169231 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": 95291, "vin": [ { "gen": { "height": 95281 } } ], "vout": [ { "amount": 296684776105, "target": { "key": "17d2b9d1538a4e8c35bcff9383c051dcaced5dd4545e1a4abe9b38a805329cdd" } } ], "extra": [ 1, 158, 154, 27, 249, 30, 134, 14, 44, 143, 58, 72, 194, 12, 107, 89, 234, 206, 129, 222, 33, 237, 94, 222, 104, 112, 25, 255, 251, 44, 36, 17, 144, 2, 17, 0, 0, 4, 119, 168, 106, 26, 101, 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