Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95a39c536acd06b7d959363fe4d75b04ba2271ccacb242a3c761be53f975acf8

Tx prefix hash: 29017f9b7a86bef95af79ab8dfb2c03be44c0006cff8c08a15c377190ade2f6b
Tx public key: e003af664465f3c1e92d562b279c05890ebc698c85c5c75b844c3045db70c853
Timestamp: 1693347977 Timestamp [UCT]: 2023-08-29 22:26:17 Age [y:d:h:m:s]: 01:133:21:13:24
Block: 836777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357030 RingCT/type: yes/0
Extra: 01e003af664465f3c1e92d562b279c05890ebc698c85c5c75b844c3045db70c853021100000005e6d27f9c000000000000000000

1 output(s) for total of 1.036121087000 dcy

stealth address amount amount idx
00: 05c1513f575afb07d65bfb9921d7c5d3a34e24ddb7f33d71354c9bde15ab76ca 1.036121087000 1289375 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": 836787, "vin": [ { "gen": { "height": 836777 } } ], "vout": [ { "amount": 1036121087, "target": { "key": "05c1513f575afb07d65bfb9921d7c5d3a34e24ddb7f33d71354c9bde15ab76ca" } } ], "extra": [ 1, 224, 3, 175, 102, 68, 101, 243, 193, 233, 45, 86, 43, 39, 156, 5, 137, 14, 188, 105, 140, 133, 197, 199, 91, 132, 76, 48, 69, 219, 112, 200, 83, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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