Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95c59b6e9954594e612c0c2e43a749dbbce78462435c9715c6b40bba5c93d4e8

Tx prefix hash: 87c9fa9a79df2c2525a49c5124de5edfa927c5430ae622e5dbe5a5c514502c73
Tx public key: 994b457c769ba618445727a2d64f25e9a8d339d456ab1fa83f2406dc9b69c6c4
Timestamp: 1700910974 Timestamp [UCT]: 2023-11-25 11:16:14 Age [y:d:h:m:s]: 01:148:17:53:48
Block: 899300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367474 RingCT/type: yes/0
Extra: 01994b457c769ba618445727a2d64f25e9a8d339d456ab1fa83f2406dc9b69c6c4021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.643051517000 dcy

stealth address amount amount idx
00: fa53fa3d046d9d306e82a1e1c9a66e29c6e8449e3bac57b0ee63315326ebaea7 0.643051517000 1355747 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": 899310, "vin": [ { "gen": { "height": 899300 } } ], "vout": [ { "amount": 643051517, "target": { "key": "fa53fa3d046d9d306e82a1e1c9a66e29c6e8449e3bac57b0ee63315326ebaea7" } } ], "extra": [ 1, 153, 75, 69, 124, 118, 155, 166, 24, 68, 87, 39, 162, 214, 79, 37, 233, 168, 211, 57, 212, 86, 171, 31, 168, 63, 36, 6, 220, 155, 105, 198, 196, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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