Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 879156c34459a1c16d8bf4ff20c8b261fe97a177dc7588c33335e18d01d30b61

Tx prefix hash: a3c51ceb138469711dd038c528a6714992b5415ccd0acf61d3b27172bcf26454
Tx public key: e58e42fb06530b88dbb61c743c576a80571e53f646681adf6309a65767c12f6b
Timestamp: 1709199197 Timestamp [UCT]: 2024-02-29 09:33:17 Age [y:d:h:m:s]: 01:106:21:41:09
Block: 968017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337362 RingCT/type: yes/0
Extra: 01e58e42fb06530b88dbb61c743c576a80571e53f646681adf6309a65767c12f6b0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fac9c246079c254e4f909bfc27127e58c0d7094811a8ea67a01e568451cdad3c 0.600000000000 1427814 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": 968027, "vin": [ { "gen": { "height": 968017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fac9c246079c254e4f909bfc27127e58c0d7094811a8ea67a01e568451cdad3c" } } ], "extra": [ 1, 229, 142, 66, 251, 6, 83, 11, 136, 219, 182, 28, 116, 60, 87, 106, 128, 87, 30, 83, 246, 70, 104, 26, 223, 99, 9, 166, 87, 103, 193, 47, 107, 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