Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba86bcbe0b621681c9684fde0a956e5a3f9a814df6e91e77b6918d874bcf8fda

Tx prefix hash: 7d484945f54330c75736e8f2b761056205ade38396c16e4978b857c83af34d0b
Tx public key: c2d7c050cfd2019af3a9f2afcf29232dc15f240b7a31aefedc061b8ebaebc426
Timestamp: 1673176076 Timestamp [UCT]: 2023-01-08 11:07:56 Age [y:d:h:m:s]: 02:304:23:30:35
Block: 670222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 737369 RingCT/type: yes/0
Extra: 01c2d7c050cfd2019af3a9f2afcf29232dc15f240b7a31aefedc061b8ebaebc42602110000000152542ceb000000000000000000

1 output(s) for total of 3.692123746000 dcy

stealth address amount amount idx
00: b6cd00f01aabebcdf0a7de38361116e551c467a7122fe347c95de968d17ed44d 3.692123746000 1111611 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": 670232, "vin": [ { "gen": { "height": 670222 } } ], "vout": [ { "amount": 3692123746, "target": { "key": "b6cd00f01aabebcdf0a7de38361116e551c467a7122fe347c95de968d17ed44d" } } ], "extra": [ 1, 194, 215, 192, 80, 207, 210, 1, 154, 243, 169, 242, 175, 207, 41, 35, 45, 193, 95, 36, 11, 122, 49, 174, 254, 220, 6, 27, 142, 186, 235, 196, 38, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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