Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f79c672d2fd99589894fca6d7ab47c83e078dd2f7e740f329204511dd297dd40

Tx prefix hash: 5471f9c1f5d132fa4bf032c9a1b596f948e42ac96603d342d9f6f30fe4a80ba2
Tx public key: 2240168e5fbe0fb76ef262ec836c3e46e2937bdfc1f3ed73353f1e81dbe52e58
Timestamp: 1718751701 Timestamp [UCT]: 2024-06-18 23:01:41 Age [y:d:h:m:s]: 00:166:08:38:38
Block: 1047210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119066 RingCT/type: yes/0
Extra: 012240168e5fbe0fb76ef262ec836c3e46e2937bdfc1f3ed73353f1e81dbe52e580211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 763ba3d22c06e7bbddbd04a5d8fff5879c0bca0aaba49f9093cce111799c774e 0.600000000000 1517029 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": 1047220, "vin": [ { "gen": { "height": 1047210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "763ba3d22c06e7bbddbd04a5d8fff5879c0bca0aaba49f9093cce111799c774e" } } ], "extra": [ 1, 34, 64, 22, 142, 95, 190, 15, 183, 110, 242, 98, 236, 131, 108, 62, 70, 226, 147, 123, 223, 193, 243, 237, 115, 53, 63, 30, 129, 219, 229, 46, 88, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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