Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3f70788a79da7391c9d99b0bdc5ec3867ed700fe83358d85542c62890fcaa9e

Tx prefix hash: 2d47f23540be93f92b2496298b597076c2b22a1886cba836d62d74862d552efd
Tx public key: d077416f22aec6fc855318ccdf70726354e281c825a5a66d107f1cb7032cf62c
Timestamp: 1717900570 Timestamp [UCT]: 2024-06-09 02:36:10 Age [y:d:h:m:s]: 00:339:05:16:40
Block: 1040154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242451 RingCT/type: yes/0
Extra: 01d077416f22aec6fc855318ccdf70726354e281c825a5a66d107f1cb7032cf62c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e0fbe5501d19e4bcf48a1605acfe286d914557ea4cac7d0cc824f6a59664a1f 0.600000000000 1508811 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": 1040164, "vin": [ { "gen": { "height": 1040154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e0fbe5501d19e4bcf48a1605acfe286d914557ea4cac7d0cc824f6a59664a1f" } } ], "extra": [ 1, 208, 119, 65, 111, 34, 174, 198, 252, 133, 83, 24, 204, 223, 112, 114, 99, 84, 226, 129, 200, 37, 165, 166, 109, 16, 127, 28, 183, 3, 44, 246, 44, 2, 17, 0, 0, 0, 3, 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