Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf2453e1e9ccc8eb8287f24bfd0c7893bb54f57f6dfffe44abb4bab21e419f1d

Tx prefix hash: 5db2e682181c45ee56594c7b38a7e662f13a4423d78fb3d74a5e99bf6f22def9
Tx public key: e47ee6ec8c2dc6111c5efbdf3701f0c4a1b8cc4d89ba0eed764ca7f4b0f36c33
Timestamp: 1737156051 Timestamp [UCT]: 2025-01-17 23:20:51 Age [y:d:h:m:s]: 00:058:13:12:38
Block: 1199635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41636 RingCT/type: yes/0
Extra: 01e47ee6ec8c2dc6111c5efbdf3701f0c4a1b8cc4d89ba0eed764ca7f4b0f36c330211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9aa10d215cef29cb08e60fe8a070fa6b3fcf15497e3ba663d0211c1e41b6cf4 0.600000000000 1686268 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": 1199645, "vin": [ { "gen": { "height": 1199635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9aa10d215cef29cb08e60fe8a070fa6b3fcf15497e3ba663d0211c1e41b6cf4" } } ], "extra": [ 1, 228, 126, 230, 236, 140, 45, 198, 17, 28, 94, 251, 223, 55, 1, 240, 196, 161, 184, 204, 77, 137, 186, 14, 237, 118, 76, 167, 244, 176, 243, 108, 51, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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