Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dc87eea723893a1283d664447df63b275468b89a35e883aca32475991c8f8cc

Tx prefix hash: 7eb4460a650181591ec1e453a94f2d639c48abeae86d87386eb9e31d3e7fc090
Tx public key: 87f4f91cb47296af9c42f999615147bac6bb7edc9a93d402cc8f276b45bd16a0
Timestamp: 1721805915 Timestamp [UCT]: 2024-07-24 07:25:15 Age [y:d:h:m:s]: 00:257:11:42:08
Block: 1072519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183938 RingCT/type: yes/0
Extra: 0187f4f91cb47296af9c42f999615147bac6bb7edc9a93d402cc8f276b45bd16a0021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b745cc4400cd0eaf6f64f8025f2e0bc5eba73da42e93b427b7e83c2ab7a029a 0.600000000000 1544992 of 15

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": 1072529, "vin": [ { "gen": { "height": 1072519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b745cc4400cd0eaf6f64f8025f2e0bc5eba73da42e93b427b7e83c2ab7a029a" } } ], "extra": [ 1, 135, 244, 249, 28, 180, 114, 150, 175, 156, 66, 249, 153, 97, 81, 71, 186, 198, 187, 126, 220, 154, 147, 212, 2, 204, 143, 39, 107, 69, 189, 22, 160, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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