Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c57a94c12c750ddc2b05776089daf1848f935fd52e5c4bb83d8dd104af82ed75

Tx prefix hash: 3be8e54260c4d56074db5bc0418988ee9d901afee4dde3819ee0c03c88ae131f
Tx public key: 1b1b3006f5f1df8f1a85710d9c24a692452b67d16bb4cf6d85e68946a7babca2
Timestamp: 1726133836 Timestamp [UCT]: 2024-09-12 09:37:16 Age [y:d:h:m:s]: 00:278:13:00:01
Block: 1108402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198835 RingCT/type: yes/0
Extra: 011b1b3006f5f1df8f1a85710d9c24a692452b67d16bb4cf6d85e68946a7babca202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8399303d004ce7a57588d8998b136aa23bcca53ea34f9d5336a200ee8c678ee 0.600000000000 1586285 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": 1108412, "vin": [ { "gen": { "height": 1108402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8399303d004ce7a57588d8998b136aa23bcca53ea34f9d5336a200ee8c678ee" } } ], "extra": [ 1, 27, 27, 48, 6, 245, 241, 223, 143, 26, 133, 113, 13, 156, 36, 166, 146, 69, 43, 103, 209, 107, 180, 207, 109, 133, 230, 137, 70, 167, 186, 188, 162, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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