Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d99f66ba6eade9f931f65334fad99db8181d6c61343dcb59c0b8f3a3f3719463

Tx prefix hash: 4f36d018bc4cf32bb4b7678505e211d1ae1dafebf16170b70933bfaf0062cf0b
Tx public key: c200f8d13f07e84d5a95ccf4f23339bf90c0e11a89688c61ad7f0bdd86ebd360
Timestamp: 1725038721 Timestamp [UCT]: 2024-08-30 17:25:21 Age [y:d:h:m:s]: 00:220:23:30:14
Block: 1099325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157789 RingCT/type: yes/0
Extra: 01c200f8d13f07e84d5a95ccf4f23339bf90c0e11a89688c61ad7f0bdd86ebd360021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cf2ae87977173d30bf2f02f2acf4e665a4ac7b7ed79320ab406bbaab54a64c7 0.600000000000 1575284 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": 1099335, "vin": [ { "gen": { "height": 1099325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cf2ae87977173d30bf2f02f2acf4e665a4ac7b7ed79320ab406bbaab54a64c7" } } ], "extra": [ 1, 194, 0, 248, 209, 63, 7, 232, 77, 90, 149, 204, 244, 242, 51, 57, 191, 144, 192, 225, 26, 137, 104, 140, 97, 173, 127, 11, 221, 134, 235, 211, 96, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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