Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be0108b18f595ebfb8722d716bab6107ff770ce2a23d88c76042f49fc4f2a9e4

Tx prefix hash: f09fb2909957a0cc2e898d0541ca5836817ac466a114109306bdaf73fad961b2
Tx public key: 1d32b31e9c60f0b138e7c3e667c26972d6c347d57eec88d10b2c57855c7e53a8
Timestamp: 1705127325 Timestamp [UCT]: 2024-01-13 06:28:45 Age [y:d:h:m:s]: 01:094:21:27:50
Block: 934232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328932 RingCT/type: yes/0
Extra: 011d32b31e9c60f0b138e7c3e667c26972d6c347d57eec88d10b2c57855c7e53a802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe725c115395a662ba2f1b57cb39d7680eeda6c6b9b76cea29d80669b37779ba 0.600000000000 1392222 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": 934242, "vin": [ { "gen": { "height": 934232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe725c115395a662ba2f1b57cb39d7680eeda6c6b9b76cea29d80669b37779ba" } } ], "extra": [ 1, 29, 50, 179, 30, 156, 96, 240, 177, 56, 231, 195, 230, 103, 194, 105, 114, 214, 195, 71, 213, 126, 236, 136, 209, 11, 44, 87, 133, 92, 126, 83, 168, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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