Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b79b6e73f154ca919e2c0565757fb44925de05316b067b8971c6aaa9cb59f4a

Tx prefix hash: f56e11f5616479c6ba2614bdfc12565c2067e18c4fd280d23eef495b6dde78a7
Tx public key: c3e9b7222e6de61803f59a81dc74c4a9d28946af97f31e5188c33538ade5961c
Timestamp: 1721036054 Timestamp [UCT]: 2024-07-15 09:34:14 Age [y:d:h:m:s]: 00:304:12:36:16
Block: 1066152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217582 RingCT/type: yes/0
Extra: 01c3e9b7222e6de61803f59a81dc74c4a9d28946af97f31e5188c33538ade5961c02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3687d33f4411e64c3443a12e00dd82349de636f8acc9d4eb2eb3b9f3a1ae8365 0.600000000000 1536725 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": 1066162, "vin": [ { "gen": { "height": 1066152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3687d33f4411e64c3443a12e00dd82349de636f8acc9d4eb2eb3b9f3a1ae8365" } } ], "extra": [ 1, 195, 233, 183, 34, 46, 109, 230, 24, 3, 245, 154, 129, 220, 116, 196, 169, 210, 137, 70, 175, 151, 243, 30, 81, 136, 195, 53, 56, 173, 229, 150, 28, 2, 17, 0, 0, 0, 1, 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