Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c710d041655449857a5f2fae10ffbcea03d4be1609469b79ff51f21ba385cdf2

Tx prefix hash: 1feb0c71f774477487394ba88d377b1a04ea925f26fd3f652e4f76e4e75a074e
Tx public key: 4f2c1062dc2730cd7ff95e765a6bced13658054bf764d68794615c46f2835866
Timestamp: 1659432837 Timestamp [UCT]: 2022-08-02 09:33:57 Age [y:d:h:m:s]: 02:098:10:58:35
Block: 557008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 591750 RingCT/type: yes/0
Extra: 014f2c1062dc2730cd7ff95e765a6bced13658054bf764d68794615c46f2835866021100000003e6d27f9c000000000000000000

1 output(s) for total of 8.757928454000 dcy

stealth address amount amount idx
00: eec65f6fdf22be4c5f908a993c05dc7ace60ea4a8d99d1c1c777883547a432ac 8.757928454000 988976 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": 557018, "vin": [ { "gen": { "height": 557008 } } ], "vout": [ { "amount": 8757928454, "target": { "key": "eec65f6fdf22be4c5f908a993c05dc7ace60ea4a8d99d1c1c777883547a432ac" } } ], "extra": [ 1, 79, 44, 16, 98, 220, 39, 48, 205, 127, 249, 94, 118, 90, 107, 206, 209, 54, 88, 5, 75, 247, 100, 214, 135, 148, 97, 92, 70, 242, 131, 88, 102, 2, 17, 0, 0, 0, 3, 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