Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4d79755227823013fb41cf720d1fbec11e53d0c84fd02428a511989cc3dd373

Tx prefix hash: f03a68be0c6d498eec83b7c7bffc2a0d66843a77e61271969ec7e12d6f10f6f0
Tx public key: 54f33b90ff60be99c3ddaecb54b34c282764f4050e78b7bc3f4ecb7c3e27db7f
Timestamp: 1705632715 Timestamp [UCT]: 2024-01-19 02:51:55 Age [y:d:h:m:s]: 01:075:23:37:43
Block: 938418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315397 RingCT/type: yes/0
Extra: 0154f33b90ff60be99c3ddaecb54b34c282764f4050e78b7bc3f4ecb7c3e27db7f0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ea77c7ded93d665c2abadc212a0b521e5d0f3af92742f5dd089412dc0247624 0.600000000000 1396488 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": 938428, "vin": [ { "gen": { "height": 938418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ea77c7ded93d665c2abadc212a0b521e5d0f3af92742f5dd089412dc0247624" } } ], "extra": [ 1, 84, 243, 59, 144, 255, 96, 190, 153, 195, 221, 174, 203, 84, 179, 76, 40, 39, 100, 244, 5, 14, 120, 183, 188, 63, 78, 203, 124, 62, 39, 219, 127, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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