Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 864c43761de12dcf4b03ed5ab816dcca3bb7448c32de81bb9755fdbaadb21ac6

Tx prefix hash: d1c8549185ee7ee9c16300665c0e3222bdfeb6f909752ffbb94c5484e3ebf8fb
Tx public key: ca832e9883de1947457d50a4aece6bc88979db6fc5fd0b3b38884883c2bcf5c5
Timestamp: 1700853933 Timestamp [UCT]: 2023-11-24 19:25:33 Age [y:d:h:m:s]: 02:041:15:26:49
Block: 898831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 549600 RingCT/type: yes/0
Extra: 01ca832e9883de1947457d50a4aece6bc88979db6fc5fd0b3b38884883c2bcf5c5021100000014faf35c9c000000000000000000

1 output(s) for total of 0.645356605000 dcy

stealth address amount amount idx
00: de3816134c3051b4b66549fe73a9810ba3a8cc53b066b941d3ef4d15f66b1a6f 0.645356605000 1355266 of 0

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": 898841, "vin": [ { "gen": { "height": 898831 } } ], "vout": [ { "amount": 645356605, "target": { "key": "de3816134c3051b4b66549fe73a9810ba3a8cc53b066b941d3ef4d15f66b1a6f" } } ], "extra": [ 1, 202, 131, 46, 152, 131, 222, 25, 71, 69, 125, 80, 164, 174, 206, 107, 200, 137, 121, 219, 111, 197, 253, 11, 59, 56, 136, 72, 131, 194, 188, 245, 197, 2, 17, 0, 0, 0, 20, 250, 243, 92, 156, 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