Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6e91bc9727a188d5adcdee81e3b0a237ee84f96a9f5e6b0f684ca076681fc34

Tx prefix hash: 5f37122336f7860a3c28bfd0127472bc99da30cc84e76852bbb0f277190e6385
Tx public key: f4cce83810786d8e25103e6f02dc85791319f5a75803c1a7c384b2a06d604dc6
Timestamp: 1628662372 Timestamp [UCT]: 2021-08-11 06:12:52 Age [y:d:h:m:s]: 03:175:05:32:22
Block: 311601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 898157 RingCT/type: yes/0
Extra: 01f4cce83810786d8e25103e6f02dc85791319f5a75803c1a7c384b2a06d604dc6021100000006e6f80b5a000000000000000000

1 output(s) for total of 56.955675732000 dcy

stealth address amount amount idx
00: 411c5b1acd0bd10d971ec4c7b4bcf1e37b5ab6f03a6bcb9dc05ba61a19b4c4d6 56.955675732000 648474 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": 311611, "vin": [ { "gen": { "height": 311601 } } ], "vout": [ { "amount": 56955675732, "target": { "key": "411c5b1acd0bd10d971ec4c7b4bcf1e37b5ab6f03a6bcb9dc05ba61a19b4c4d6" } } ], "extra": [ 1, 244, 204, 232, 56, 16, 120, 109, 142, 37, 16, 62, 111, 2, 220, 133, 121, 19, 25, 245, 167, 88, 3, 193, 167, 195, 132, 178, 160, 109, 96, 77, 198, 2, 17, 0, 0, 0, 6, 230, 248, 11, 90, 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