Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 491c1ceb8d85156de48b58e59d746f3dcc5884593327953db317522c516f9730

Tx prefix hash: 8c35acf078ee05f0a2d917e6ea29a9d8959f66d278f5a18e6f5b179ef6a5bf33
Tx public key: f1c0d7b86b49ccef3abad06526b06ee52d37047c6917a21c6a2e4d0b0931591d
Timestamp: 1688862017 Timestamp [UCT]: 2023-07-09 00:20:17 Age [y:d:h:m:s]: 01:274:06:11:31
Block: 799665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457129 RingCT/type: yes/0
Extra: 01f1c0d7b86b49ccef3abad06526b06ee52d37047c6917a21c6a2e4d0b0931591d021100000001faf35c9c000000000000000000

1 output(s) for total of 1.375238521000 dcy

stealth address amount amount idx
00: 3ff1d2a14ec93222fefe88a984f79e86e03dc8cfd789ed496e8e2a87388f846f 1.375238521000 1250690 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": 799675, "vin": [ { "gen": { "height": 799665 } } ], "vout": [ { "amount": 1375238521, "target": { "key": "3ff1d2a14ec93222fefe88a984f79e86e03dc8cfd789ed496e8e2a87388f846f" } } ], "extra": [ 1, 241, 192, 215, 184, 107, 73, 204, 239, 58, 186, 208, 101, 38, 176, 110, 229, 45, 55, 4, 124, 105, 23, 162, 28, 106, 46, 77, 11, 9, 49, 89, 29, 2, 17, 0, 0, 0, 1, 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