Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 470e0847e1feca26886a710e08e7a8e8794674e80a586bd1619a96d27e1d301d

Tx prefix hash: 15dbb5e53c321f97ee8c17c39f5e1bbabde4755d2aeb8992d832071db818ca91
Tx public key: c45cb99b969042c5b399674a3d43ceb8af6f552e28631ec2c36ead795f8ce276
Timestamp: 1700591938 Timestamp [UCT]: 2023-11-21 18:38:58 Age [y:d:h:m:s]: 01:136:08:56:27
Block: 896651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358634 RingCT/type: yes/0
Extra: 01c45cb99b969042c5b399674a3d43ceb8af6f552e28631ec2c36ead795f8ce27602110000000775e3f0e9000000000000000000

1 output(s) for total of 0.656180028000 dcy

stealth address amount amount idx
00: 46a276ad346919c59e4fbe980b9794ad55f118eadf625bf29381e1562a61fe44 0.656180028000 1352992 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": 896661, "vin": [ { "gen": { "height": 896651 } } ], "vout": [ { "amount": 656180028, "target": { "key": "46a276ad346919c59e4fbe980b9794ad55f118eadf625bf29381e1562a61fe44" } } ], "extra": [ 1, 196, 92, 185, 155, 150, 144, 66, 197, 179, 153, 103, 74, 61, 67, 206, 184, 175, 111, 85, 46, 40, 99, 30, 194, 195, 110, 173, 121, 95, 140, 226, 118, 2, 17, 0, 0, 0, 7, 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