Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1686c175e472a28197eff40344447fe40e8c5fb7ef58427783b8bf7a25528f16

Tx prefix hash: 874b6867b3db265d9142666a65972a73d0ffd7f87889f20e543aace5ac3ad21b
Tx public key: c22ae2e8c7fb7e02b9e4de18684aa086451e7112b51ca0a4e4a66ff47d057bfc
Timestamp: 1693360966 Timestamp [UCT]: 2023-08-30 02:02:46 Age [y:d:h:m:s]: 01:223:09:56:47
Block: 836889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420801 RingCT/type: yes/0
Extra: 01c22ae2e8c7fb7e02b9e4de18684aa086451e7112b51ca0a4e4a66ff47d057bfc02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.035236104000 dcy

stealth address amount amount idx
00: 6d9c10e4b9f8f95864fe142fbca8cf9fae6a24a7b781ee42fc64af9635d62db0 1.035236104000 1289495 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": 836899, "vin": [ { "gen": { "height": 836889 } } ], "vout": [ { "amount": 1035236104, "target": { "key": "6d9c10e4b9f8f95864fe142fbca8cf9fae6a24a7b781ee42fc64af9635d62db0" } } ], "extra": [ 1, 194, 42, 226, 232, 199, 251, 126, 2, 185, 228, 222, 24, 104, 74, 160, 134, 69, 30, 113, 18, 181, 28, 160, 164, 228, 166, 111, 244, 125, 5, 123, 252, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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